[JIRA] [git-plugin] (JENKINS-24809) Github-Jenkins Trigger issue with slave
Title: Message Title Kenneth Baltrinic commented on JENKINS-24809 Re: Github-Jenkins Trigger issue with slave Mark Waite It took me a while get back to this. I have upgraded our git client to 1.18.0 but we are still experiencing the same problem as I detailed above. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-24809) Github-Jenkins Trigger issue with slave
Title: Message Title Mark Waite commented on JENKINS-24809 Re: Github-Jenkins Trigger issue with slave Kenneth Baltrinic have you tried the alternative I suggested in my previous comment, changing the Jenkins configured path for the git executable from C:\Program Files (x86)\Git\cmd\git.exe to C:\Program Files (x86)\Git\bin\git.exe Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-24809) Github-Jenkins Trigger issue with slave
Title: Message Title Mark Waite commented on JENKINS-24809 Re: Github-Jenkins Trigger issue with slave I think the problem you're seeing is due to JENKINS-28943 and is resolved in git client plugin 1.18.0. I'm surprised you didn't update to git client plugin 1.18.0 at the same time you updated to git plugin 2.4.0. If that does not fix it, then you can also work-around the problem by changing the path to the git executable on those computers from C:\Program Files (x86)\Git\cmd\git.exe to C:\Program Files (x86)\Git\bin\git.exe Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-24809) Github-Jenkins Trigger issue with slave
Title: Message Title Kenneth Baltrinic commented on JENKINS-24809 Re: Github-Jenkins Trigger issue with slave Mark Waite I would like to re-open this issue. We are encountering the exact same behavior, though our setup is a bit different. We are not using git hooks in our case, simple SCM Polling. As with the originally reported situation, this is happening with a Linux master an multiple (8) windows slaves. All slaves are presenting with the same issue. Setting Force polling workspace also works as a workaround in our case. We are seeing this with Jenkins 1.609.1, Git 2.4, Git client 1.16.1 Below is our stack trace, though it does not seem to differ materially from the one in the original report: Started on Aug 4, 2015 12:37:01 PM Polling SCM changes on hq-jenwin-007 Using strategy: Default [poll] Last Built Revision: Revision c61ffa28bf6375f1907d49cc7c5ad282c32c5f1c (refs/remotes/origin/prod) using GIT_SSH to set credentials Credential ID: ** C:\Program Files (x86)\Git\cmd\git.exe --version # timeout=10 C:\Program Files (x86)\Git\cmd\git.exe ls-remote -h ssh://git@stash:7999/**/**.git # timeout=10 FATAL: hudson.plugins.git.GitException: Error performing command: C:\Program Files (x86)\Git\cmd\git.exe ls-remote -h ssh://git@stash:7999/**/**.git hudson.util.IOException2: hudson.plugins.git.GitException: Error performing command: C:\Program Files (x86)\Git\cmd\git.exe ls-remote -h ssh://git@stash:7999/**/**.git at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:529) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at org.jenkinsci.plugins.multiplescms.MultiSCM.compareRemoteRevisionWith(MultiSCM.java:100) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1467) at hudson.model.AbstractProject._poll(AbstractProject.java:1438) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:510) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:539) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: hudson.plugins.git.GitException: Error performing command: C:\Program Files (x86)\Git\cmd\git.exe ls-remote -h ssh://git@stash:7999/**/**.git at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1598) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1277) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1268) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:2327) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:583) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:527) ... 15 more Caused by: java.io.IOException: Cannot run program C:\Program Files (x86)\Git\cmd\git.exe: error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at
[JIRA] [git-plugin] (JENKINS-24809) Github-Jenkins Trigger issue with slave
Title: Message Title Kenneth Baltrinic commented on JENKINS-24809 Re: Github-Jenkins Trigger issue with slave I should have added that we recently upgraded from an old version of jenkins where we were not seeing this behavior: Our old system was Jenkins 1.552, Git plugin 1.4 and Git Client plugin 1.6. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-24809) Github-Jenkins Trigger issue with slave
Mark Waite closed JENKINS-24809 as Cannot Reproduce Github-Jenkins Trigger issue with slave Change By: Mark Waite (28/Dec/14 5:33 AM) Status: Resolved Closed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
