My technique is the opposite of Slide's. I always use the git executable in the bin directory. There were issues reported when the git executable in the cmd directory was used instead of using the executable in the bin directory.
You might consider a "test drive" of the JGit implementation in your environment to see if it behaves any differently. The JGit implementation does not have all the features of the command line git implementation, but it may be sufficient for your use case. Was this job upgraded from a previous Git plugin version? If so, have you defined the credentials and configured the job to use those credentials? Is there some environment variable that is causing those unexpected "trace:" and "run_command:" strings in the output? I don't see those in my use of command line git on Windows. On Tue, Feb 11, 2014 at 4:59 PM, Slide <slide.o....@gmail.com> wrote: > What is the path to Git? I use the one in ProgramFiles\Git\cmd instead of > ProgramFiles\Git\bin. > > > On Tue, Feb 11, 2014 at 4:49 PM, Dunnigan, Terrence J < > terrence.j.dunni...@boeing.com> wrote: > >> Hi all, >> >> >> >> I've run into an issue where the latest git plugin / git client plugins >> time out. It pulls down the files in .git\objects\pack and elsewhere, but >> nothing beyond the .git folder. >> >> >> >> Here's my setup: >> >> >> >> Jenkins server: >> >> Jenkins LTS 1.532.1 running on a Windows 7 PC >> >> Jenkins GIT client plugin 1.6.2 (also on 1.6.1) >> >> Jenkins GIT plugin 2.0.1 >> >> >> >> Windows 7 slave PC: >> >> Jenkins is running as a service using an administrative account >> >> Git 1.8.3 is installed, along with PuTTY. >> >> GIT_SSH is set to C:\PuTTY\plink.exe >> >> Path includes C:\PuTTY >> >> >> >> Here's the error message once I hit 10 minutes: >> >> >> >> Started by user Terry Dunnigan >> >> Building remotely on slave in workspace C:\hudson_remote\workspace\job name >> >> Cloning the remote Git repository >> >> Cloning repository g...@myrepo.git >> >> Fetching upstream changes from g...@myrepo.git >> >> using GIT_SSH to set credentials >> >> Fetching upstream changes from g...@myrepo.git >> >> using GIT_SSH to set credentials >> >> ERROR: Timeout after 10 minutes >> >> FATAL: Failed to fetch from g...@myrepo.git >> >> hudson.plugins.git.GitException >> <http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException>: >> Failed to fetch from g...@myrepo.git >> >> at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:625) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.git.GitSCM.fetchFrom&entity=method> >> >> at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:847) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.git.GitSCM.retrieveChanges&entity=method> >> >> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:872) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.git.GitSCM.checkout&entity=method> >> >> at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractProject.checkout&entity=method> >> >> at >> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) >> >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout&entity=method> >> >> at >> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) >> <http://stacktrace.jenkins-ci.org/search/?query=jenkins.scm.SCMCheckoutStrategy.checkout&entity=method> >> >> at >> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) >> >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.run&entity=method> >> >> at hudson.model.Run.execute(Run.java:1665) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute&entity=method> >> >> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuild.run&entity=method> >> >> at >> hudson.model.ResourceController.execute(ResourceController.java:88) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute&entity=method> >> >> at hudson.model.Executor.run(Executor.java:246) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run&entity=method> >> >> Caused by: hudson.plugins.git.GitException >> <http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException>: >> Command "git fetch --tags --progress g...@myrepo.git >> +refs/heads/*:refs/remotes/origin/*" returned status code -1: >> >> >> >> stderr: trace: built-in: git 'fetch' '--tags' '--progress' 'g...@myrepo.git' >> '+refs/heads/*:refs/remotes/origin/*' >> >> trace: run_command: >> 'C:\Users\me\AppData\Local\Temp\ssh6588671275929067852.bat' 'g...@myrepo.git' >> 'git-upload-pack '\''myrepo.git'\''' >> >> >> >> trace: run_command: 'rev-list' '--objects' '--stdin' '--not' '--all' >> '--quiet' >> >> trace: run_command: 'rev-list' '--objects' '--stdin' '--not' '--all' >> >> trace: built-in: git 'rev-list' '--objects' '--stdin' '--not' '--all' >> >> >> >> >> >> Any thoughts? >> >> >> >> Thanks everyone. >> >> >> >> Terry Dunnigan >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Website: http://earl-of-code.com > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.