[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Josh Santangelo
commented on JENKINS-20387
git submodule update timeout value should be configurable per job
I'm disappointed to report that I can still reproduce this issue. I have Jenkins 1.585, git plugin 2.2.7, and git client plugin 1.11.0. The last comment here says it's fixed in git plugin 2.3, but that was three months ago. Is 2.3 on the way?
In any case, I have been using the same test project as mentioned earlier, configured with a 240 minute timeout on submodules. The output is below. You can see the timeouts in the output, but it seems like they are commented out.
{{
Building in workspace C:\Jenkins\jobs\git-test\workspace
Cloning the remote Git repository
Cloning repository g...@github.com:stimulant/IMR4.git
C:\Program Files (x86)\Git\cmd\git.exe init C:\Jenkins\jobs\git-test\workspace # timeout=10
Fetching upstream changes from g...@github.com:stimulant/IMR4.git
C:\Program Files (x86)\Git\cmd\git.exe --version # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe fetch --tags --progress g...@github.com:stimulant/IMR4.git +refs/heads/:refs/remotes/origin/ # timeout=240
C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.url g...@github.com:stimulant/IMR4.git # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.url g...@github.com:stimulant/IMR4.git # timeout=10
Fetching upstream changes from g...@github.com:stimulant/IMR4.git
C:\Program Files (x86)\Git\cmd\git.exe fetch --tags --progress g...@github.com:stimulant/IMR4.git +refs/heads/:refs/remotes/origin/ # timeout=240
C:\Program Files (x86)\Git\cmd\git.exe rev-parse "refs/remotes/origin/dev^{commit}" # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe rev-parse "refs/remotes/origin/origin/dev^{commit}" # timeout=10
Checking out Revision 696e4dea88730d445406e6a7dd5101b00be2d751 (refs/remotes/origin/dev)
C:\Program Files (x86)\Git\cmd\git.exe config core.sparsecheckout # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe checkout -f 696e4dea88730d445406e6a7dd5101b00be2d751 # timeout=240
C:\Program Files (x86)\Git\cmd\git.exe rev-list 696e4dea88730d445406e6a7dd5101b00be2d751 # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe remote # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe submodule init # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe submodule sync # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe config --get remote.origin.url # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe submodule update --init --recursive
ERROR: Timeout after 10 minutes
FATAL: Command "C:\Program Files (x86)\Git\cmd\git.exe submodule update --init --recursive" returned status code -1:
}}
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.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Mark Waite commented on JENKINS-20387 git submodule update timeout value should be configurable per job No, git plugin 2.3 has not released. The 2.3 beta 4 release is available in the experimental update center. Since you're using Jenkins 1.585, you can use the experimental update center and install 2.3 beta 4. The 2.3 beta 4 release should be very nearly the same quality and stability as the pre-release 2.2.8 version of the plugin. They've been kept in close synchronization. The git plugin 2.3 is not likely to release from beta very soon, because it depends on Jenkins version 1.568 or newer. The git plugin is used by so many installations that we generally don't require a Jenkins version that is newer than about 1 year old. That allows users of "stable" Jenkins servers to continue installing newer versions of plugin without requiring that they upgrade their Jenkins version. Currently, that means the git plugin supports Jenkins 1.509 and newer. Soon we may switch to require at least Jenkins 1.532, but it will likely be 6+ months before the plugin is ready to support Jenkins 1.580 (the first long term support version after 1.568). 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.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Josh Santangelo commented on JENKINS-20387 git submodule update timeout value should be configurable per job Thanks for your reply. I am now on git plugin 2.3-beta-4. I see the same result. In the output above, note the "# timeout=NN" at the end of each command. I'm still seeing that with the new plugin. I'm guessing that comments out the timeout argument. 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.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Daniel Beck commented on JENKINS-20387 git submodule update timeout value should be configurable per job Josh Santangelo: Timeout as being shown is only informational, as it's not a command argument, but how Jenkins waits for the process to quit. https://github.com/jenkinsci/git-client-plugin/blob/53fd10a7601906cb80c5fbf56d8639de747d29d8/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1427 https://github.com/jenkinsci/git-client-plugin/blob/53fd10a7601906cb80c5fbf56d8639de747d29d8/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1431 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.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Mark Waite commented on JENKINS-20387 git submodule update timeout value should be configurable per job 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.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Josh Santangelo commented on JENKINS-20387 git submodule update timeout value should be configurable per job I had the extended timeout in the "advanced clone behaviours" and "advanced checkout behaviours" sections. I did not have it in "advanced submodules behaviours". When I configured it there, it seemed to work correctly. All three of these claim to honor "org.jenkinsci.plugins.gitclient.Git.timeout" in their help text. If I set that globally, will it be permanently sorted for all jobs? Thanks again for your help. 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.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Mark Waite commented on JENKINS-20387 git submodule update timeout value should be configurable per job If you set that property, as far as I know, it will be honored for all jobs which execute on that node and do not set a timeout value. Jobs on other nodes (slaves, for example) will not honor that setting unless you set the property in the slave java virtual machine. 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.
