[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job

Fri, 31 Oct 2014 18:52:20 -0700

Mark Waite commented on Bug JENKINS-20387

I am not sure why you're not seeing it in the log file. I used git plugin 2.2.7 with git client plugin 1.11.0, opened the "Advanced submodules" and set the timeout in minutes for submodule operations to 39. That gave the following output on initial build:

First time build. Skipping changelog.
 > git remote # timeout=10
 > git submodule init # timeout=10
 > git submodule sync # timeout=10
 > git config --get remote.origin.url # timeout=10
 > git submodule update # timeout=39



When I ran that same build a second time, it reported:





Checking out Revision 021ab742e3593a863a39584f2309be22cf7a9307 (refs/remotes/origin/tests/getSubmodules)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 021ab742e3593a863a39584f2309be22cf7a9307
 > git rev-list 021ab742e3593a863a39584f2309be22cf7a9307 # timeout=10
 > git remote # timeout=10
 > git submodule init # timeout=10
 > git submodule sync # timeout=10
 > git config --get remote.origin.url # timeout=10
 > git submodule update # timeout=39






Did you set the timeout value in the "Advanced submodules" section of the job configuration, or somewhere else?
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.

Reply via email to