Daniel Haskin
commented on JENKINS-13634
Multiple SCM plugin fails when used with matrix project and git plugin
Happened to me too. I run a multi-configuration job on multiple slaves using the GIT plugin to check things out. Here's my output:
Started by an SCM change
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Adding build parameters as variables.
[EnvInject] - Injecting as environment variables the properties content
JAVA_OPTS=-XX:MaxPermSize=384m
REPOSITORY=deploysnapshots
[EnvInject] - Variables injected successfully.
[EnvInject] - Injecting contributions.
Building remotely on cent6-build in workspace /tmp/jenkins/workspace/[Project-Name Omitted]
Checkout:[Project-Name Omitted] / /tmp/jenkins/workspace/[Project-Name Omitted] - hudson.remoting.Channel@1dc80063:[CentOS 6 Host (name omitted)]
Using strategy: Default
Last Built Revision: Revision 3f5369bc257e7d2ccdf112d388b7189fe56c8c0c (origin/master)
Fetching changes from 1 remote Git repository
Fetching upstream changes from https://[server_name_omitted]/git/[repository_name_omitted]
Commencing build of Revision 22c81e370bec334029c0ab2be4135b7f2a9de75e (origin/master)
Checking out Revision 22c81e370bec334029c0ab2be4135b7f2a9de75e (origin/master)
FATAL: Could not checkout null with start point 22c81e370bec334029c0ab2be4135b7f2a9de75e
hudson.plugins.git.GitException: Could not checkout null with start point 22c81e370bec334029c0ab2be4135b7f2a9de75e
at hudson.plugins.git.GitAPI.checkoutBranch(GitAPI.java:872)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1284)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1268)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2180)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git checkout -f 22c81e370bec334029c0ab2be4135b7f2a9de75e" returned status code 128:
stdout:
stderr: fatal: unable to read tree e43b730994887987271f0c1aca18bca8426a6e1b
at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:779)
at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:741)
at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:751)
at hudson.plugins.git.GitAPI.checkoutBranch(GitAPI.java:859)
... 12 more
Information from the build lead on the project:
This happens at least once a week on one git checkout job. It seems to be random when it starts, but typically I've noticed it the next morning when I come in. (ie it happens overnight).
When this happens it is quite a large problem as it still detects that the SCM was updated and so tries to poll it every 3 minutes still, even though the build fails everytime. This results in 100+ emails if gone unchecked overnight.
Wiping out the workspace solves the problem completely.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
