-
Bug
-
Resolution: Cannot Reproduce
-
Minor
-
Jenkins Master: 1.65.3; Git Plugin: 2.2.7
Slave: Ubuntu 10.0.4 LTS
Used to work on git 2.2.1. After upgrading to 2.2.7, it cannot work on Linux slave. But can work on windows slave.
Errors from polling log:
Started on Oct 21, 2014 10:31:00 PM
Polling SCM changes on VM-Platuypus-Build-10.110.61.85-PDK
Using strategy: Default
[poll] Last Built Revision: Revision cd2cd96d9ff5f3ca90ead6178f299a873978a44c (origin/master)
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repositories
> git config remote.origin.url ssh://bmcdiags@10.110.61.117:30000/platypus.git # timeout=10
Fetching upstream changes from ssh://bmcdiags@10.110.61.117:30000/platypus.git
> git --version # timeout=10
> git fetch --tags ssh://bmcdiags@10.110.61.117:30000/platypus.git +refs/heads/:refs/remotes/origin/ # timeout=20
FATAL: hudson.plugins.git.GitException: Failed to fetch from ssh://bmcdiags@10.110.61.117:30000/platypus.git
hudson.util.IOException2: hudson.plugins.git.GitException: Failed to fetch from ssh://bmcdiags@10.110.61.117:30000/platypus.git
at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:475)
at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:357)
at hudson.scm.SCM.poll(SCM.java:374)
at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1449)
at hudson.model.AbstractProject._poll(AbstractProject.java:1420)
at hudson.model.AbstractProject.poll(AbstractProject.java:1331)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:477)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:506)
at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: hudson.plugins.git.GitException: Failed to fetch from ssh://bmcdiags@10.110.61.117:30000/platypus.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:647)
at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:554)
at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:473)
... 13 more
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags ssh://bmcdiags@10.110.61.117:30000/platypus.git +refs/heads/:refs/remotes/origin/" returned status code 128:
stdout:
stderr: error: cannot run ssh: No such file or directory
fatal: unable to fork
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1435)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1223)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:85)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:280)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
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:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
Done. Took 0.15 sec
No changes
[JENKINS-25248] GIT SCM polling failed on Linux slave
sharon xia
added a comment - @Mark, Nothing changed on jenkins as the only thing we updated is the git-plugin.
sharon xia
added a comment - @Mark, Nothing changed on jenkins as the only thing we updated is the git-plugin. I understood that you said that nothing else changed on Jenkins.
Reporting the value of the PATH variable from inside one of the jobs which is broken can help diagnose if this is the same problem as was reported in JENKINS-24516 and JENKINS-24467. If it is the same problem then that may indicate that the fix for those two bugs was either incomplete or incorrect. If it is not the same problem, then the PATH variable may not be the answer.
As an additional check, does the polling succeed if you enable "Polling requires a workspace"? That would be another indicator of the same behavior as was reported in JENKINS-24467 and JENKINS-24516.
sharon xia
added a comment - Pooling does not succeed even if we force polling using workspace sharon_xia the polling failure when you force using workspace is unexpected based on the earlier two bugs (JENKINS-24516 and JENKINS-24467). I think that may indicate there is some other bug or some other change in the environment.
Based on the current amount of information in this bug report, I cannot duplicate the bug, and you seem unwilling to give me enough information to understand how to duplicate the bug. Is there a reason why you're unwilling to report the value of the PATH variable from inside one of the failing jobs?
Can you provide detailed steps which will show the failure in a fresh installation of Jenkins?
Detailed steps to duplicate the problem have not been provided in over 6 weeks. I cannot duplicate the problem. Closing the bug as "Cannot Reproduce".
Could you add the pre-scm build step plugin and add a build step to one of your jobs which displays the value of the PATH environment variable?
I would guess you're encountering a case where the EnvInject plugin is modifying the environment of the job and that prevents the git program from finding the ssh program that it needs for communication.
The case which was reported in
JENKINS-24516andJENKINS-24467are believed to be fixed in version 2.2.6, so they should still be fixed in 2.2.7.Alternately, has something else changed in your Jenkins environment or the job definition which might make the git process have the wrong PATH on the machine running that process?