|
I'm closing this bug report because I cannot duplicate it. It contains insufficient information.
If the original author provides more information, it can be reopened (if it can be duplicated).
Things that I was able to guess from the stack trace (and which the submitter should have provided with the original submission, rather than just cutting and pasting a stack trace):
Master is running on Windows, running git client plugin 1.19.6 (likely), and git plugin 2.4.4 (possibly). Command line git is the implementation used in this stack trace.
-
User created a new job
-
User entered the URL to the repository in the URL field of the job
-
User probably did not enter any credentials for the repository (unclear, but hinted by code)
-
When the user tabbed out of the field, the InvalidObjectIdException was thrown when the git plugin asked the git client plugin to report the most recent revision on the repository
Some crucial questions that aren't answered by the stack trace include:
-
Is command line git installed on the Windows machine?
-
Are any other git commands working on the Windows machine?
-
Is the Jenkins process on the Windows machine running as a service or as a user?
-
What is the URL of the repository?
-
Does the repository require credentials, and were they provided by the user?
-
Where is the repository hosted (github, bitbucket, internal by user, etc.) and what version of the hosting software is being used?
-
What other steps had the user taken when the problem appeared?
-
Does the problem happen repeatedly on that Jenkins machine?
-
Does the problem happen repeatedly on other Jenkins machines?
-
Can the user clone the repository to that Jenkins machine from the command line?
|
