So to add another data point, when I change the credentials for git to be none, it seems to honor the 60 minute timeout. Now I just need to figure out why it even hits 60 minutes for a check out that takes < 5 min on other operating systems :/ The crenedtials plugin is ver 1.10 if that helps.
Fetching upstream changes from ssh://build@gerrit:29418/project > c:\Git\bin\git.exe --version > c:\Git\bin\git.exe fetch --tags --progress ssh://build@gerrit:29418/project +refs/heads/*:refs/remotes/origin/* ERROR: Timeout after 60 minutesFATAL <http://stacktrace.jenkins-ci.org/search?query=FATAL>: Failed to fetch from ssh://build@gerrit:29418/project thanks On Fri, May 16, 2014 at 2:23 PM, Chanda Unmack <[email protected]> wrote: > Ok - hard to find a repo here without submodules :) > > I tried a different repo that does have them, but made sure the options > for recursively checking them out was unchecked. > I thought I had specified timestamps in the console output, but I guess > not. Here's the snip before it just fails (sanitized of course): > > Started by user Chanda Unmack <http://jenkins01-clone/user/cunmack> > > [EnvInject] - Loading node environment variables. [EnvInject] - Preparing > an environment for the build. [EnvInject] - Keeping Jenkins system > variables. [EnvInject] - Keeping Jenkins build variables. [EnvInject] - > Injecting as environment variables the properties content > ANDROID_HOME=/opt/something/sdk-linux ANDROID_NDK=/opt/something/ndk > [EnvInject] - Variables injected successfully. [EnvInject] - Injecting > contributions. Building remotely on > server-bld-pc3<http://jenkins01-clone/computer/server-bld-pc3>in workspace > c:\jenkins\workspace\test-project\LABEL\WIN32\TYPE\Debug > Cloning the remote Git repository Cloning repository > ssh://build@gerrit:29418/project > > c:\Git\bin\git.exe init > c:\jenkins\workspace\test-project\LABEL\WIN32\TYPE\Debug Fetching upstream > changes from ssh://build@gerrit:29418/project > c:\Git\bin\git.exe > --version > c:\Git\bin\git.exe fetch --tags --progress > ssh://build@gerrit:29418/project > +refs/heads/*:refs/remotes/origin/* > > ERROR: Timeout after 10 minutes > > ERROR <http://stacktrace.jenkins-ci.org/search?query=ERROR>: Error cloning > remote repo 'origin'hudson.plugins.git.GitException > <http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException>: > Command "c:\Git\bin\git.exe fetch --tags --progress > ssh://build@gerrit:29418/project +refs/heads/*:refs/remotes/origin/*" > returned status code 1: > stdout: Process leaked file descriptors. See > http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for > more information > Process leaked file descriptors. See > http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for > more information > > > So the leaking file descriptors is new - will check out that wiki now :) > > > > On Fri, May 16, 2014 at 12:18 PM, Mark Waite <[email protected]>wrote: > >> The log indicates that you are using submodules. Can you attempt the >> same process with a repository that does not use submodules so that we can >> confirm the issue you're seeing is specific to submodules? >> >> Mark Waite >> >> >> On Fri, May 16, 2014 at 12:25 PM, Chanda Unmack <[email protected]> wrote: >> >>> So here's the config.xml >>> http://notepad.cc/faosseqa7 >>> >>> and here's the console output >>> http://notepad.cc/mieckuclo87 >>> >>> I didn't really see anything in the jenkins logs >>> >>> thanks for the help! >>> >>> >>> On Fri, May 16, 2014 at 10:56 AM, Mark Waite >>> <[email protected]>wrote: >>> >>>> Can you upload a copy of your job definition somewhere so that I can >>>> compare it with job definitions that are known to work with the timeout? >>>> >>>> The log file which reports the timeout would also be a help, since it >>>> may point to another failure point. >>>> >>>> There are two different timeout conditions possible with the current >>>> implementation for command line git. The timeout value specified in the >>>> advanced behaviors is used for fetch and for fetch of submodules. The >>>> timeout value you set with the command line argument is used for (at least >>>> some) other invocations of command line git (like "git checkout" and "git >>>> ls-remote"). >>>> >>>> Mark Waite >>>> >>>> >>>> On Fri, May 16, 2014 at 11:33 AM, Chanda Unmack <[email protected]>wrote: >>>> >>>>> >>>>> On Fri, May 16, 2014 at 10:01 AM, Mark Waite < >>>>> [email protected]> wrote: >>>>> >>>>>> You need to add the "Additional Behaviour" "Advanced Clone >>>>>> Behaviours" and then set the timeout value in the field which opens >>>>>> there. >>>>>> >>>>>> If you're using a Linux machine as the slave, you could also consider >>>>>> using a bare "reference repository" on the slave agent so that the clone >>>>>> could point to the existing reference copy rather than downloading >>>>>> another >>>>>> copy. >>>>>> >>>>>> Mark Waite >>>>>> >>>>>> >>>>>> On Fri, May 16, 2014 at 10:57 AM, Chanda Unmack <[email protected]>wrote: >>>>>> >>>>>>> So I wonder if anyone else is seeing this as it's causing no end of >>>>>>> headache for me. >>>>>>> My jobs fail because the git clone times out after 10 minutes. >>>>>>> >>>>>>> *09:43:13* ERROR: Timeout after 10 minutes >>>>>>> >>>>>>> >>>>>>> Jenkins 1.532.2 >>>>>>> Jenkins GIT client plugin 1.9.0 >>>>>>> Jenkins GIT plugin 2.2.1 >>>>>>> Tomact 7 >>>>>>> >>>>>>> *I've set the timeout on the project to be 60 minutes * >>>>>>> The slave is windows, connected with jnlp, I've set the jvm options >>>>>>> for the slave to have a timeout of 60 minutes >>>>>>> (-Dorg.jenkinsci.plugins.gitclient.Git.timeOut=60) >>>>>>> >>>>>>> I even changed the jenkins startup to have a longer timeout with no >>>>>>> success. I've seen other discussion on the list about the 10 minute >>>>>>> timeout >>>>>>> and that it's supposed to be configurable in the project scm area, but >>>>>>> I'm >>>>>>> not seeing that being honored. Is there somewhere else this is set? >>>>>>> >>>>>>> thanks >>>>>>> >>>>>> -- >>>>>> Thanks! >>>>>> Mark Waite >>>>>> >>>>> >>>>> >>>>> I did set the Additional Behaviour-> Advanced Clone Behaviours - >>>>> that's where I set the timeout for the project. Sorry if I wasn't clear >>>>> there. >>>>> I wish I could use Linux as a slave, we do have Linux slaves as well, >>>>> but they have other git issues that while are annoying, don't prevent the >>>>> build from succeeding (yet) >>>>> >>>>>> >>>>> >>>>> -- >>>>> *C**onfidentiality Notice:* This e-mail, including all attachments, >>>>> is confidential information of Lytro, Inc. If the reader of this e-mail is >>>>> not the intended recipient or its authorized agent, the reader is hereby >>>>> notified that any dissemination, distribution or copying of this e-mail is >>>>> prohibited. If you have received this e-mail in error, please notify the >>>>> sender by replying to this message and delete this e-mail immediately. >>>>> >>>>> -- >>>>> 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 [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> >>>> -- >>>> 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 [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> *C**onfidentiality Notice:* This e-mail, including all attachments, is >>> confidential information of Lytro, Inc. If the reader of this e-mail is not >>> the intended recipient or its authorized agent, the reader is hereby >>> notified that any dissemination, distribution or copying of this e-mail is >>> prohibited. If you have received this e-mail in error, please notify the >>> sender by replying to this message and delete this e-mail immediately. >>> >>> -- >>> 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 [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> 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 [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > *C**onfidentiality Notice:* This e-mail, including all attachments, is > confidential information of Lytro, Inc. If the reader of this e-mail is not > the intended recipient or its authorized agent, the reader is hereby > notified that any dissemination, distribution or copying of this e-mail is > prohibited. If you have received this e-mail in error, please notify the > sender by replying to this message and delete this e-mail immediately. > -- *C**onfidentiality Notice:* This e-mail, including all attachments, is confidential information of Lytro, Inc. If the reader of this e-mail is not the intended recipient or its authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
