• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: git-plugin
• Labels:

  • configuration
  • git
  • plugin
• Environment:

  Windows (8) (the slow disk access probably makes it more likely to manifest)

[JENKINS-22547] Git timeout setting does not work for checkout

Jan Hudec created issue - 2014-04-09 12:55

Jan Hudec made changes - 2014-04-09 12:58

Link

New: This issue is related to JENKINS-20445 [ JENKINS-20445 ]

Jan Hudec made changes - 2014-04-09 13:01

Link

New: This issue is related to JENKINS-11286 [ JENKINS-11286 ]

Mark Waite made changes - 2014-04-17 14:19

Resolution		New: Cannot Reproduce [ 5 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Mark Waite made changes - 2014-04-17 14:19

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]

Jan Hudec made changes - 2014-06-24 14:37

Resolution	Original: Cannot Reproduce [ 5 ]
Status	Original: Closed [ 6 ]	New: Reopened [ 4 ]

Jan Hudec made changes - 2014-06-24 16:32

Description	Original: When I configure longer timeout for git checkout in a matrix job, the master job checks out fine, but the individual configurations incorrectly abort the check out after 10 minutes.	New: Some git processes error out with {{ERROR: Timeout after 10 minutes}} even though longer timeout is configured. It affects the `git checkout` operation itself. The fetch operation is OK. The log says: {noformat} using GIT_SSH to set credentials jenkins key for git  > git fetch --tags --progress git@git.company.com:project +refs/heads/*:refs/remotes/origin/* --prune Checking out Revision 159bc2b21669bc7b5217341fc8de9cd6b48439b2 (origin/dev/jan.hudec/pu)  > git config core.sparsecheckout  > git checkout -f 159bc2b21669bc7b5217341fc8de9cd6b48439b2 ERROR: Timeout after 10 minutes FATAL: Could not checkout null with start point 159bc2b21669bc7b5217341fc8de9cd6b48439b2 {noformat}
Environment	Original: Windows (8), but I don't think it matters. Unfortunately our MacOS builder is currently broken, so I can't test there.	New: Windows (8), but I don't think it matters.
Labels	Original: git matrix plugin	New: configuration git plugin
Summary	Original: Matrix jobs don't honor git timeout setting	New: Git timeout setting does not work for checkout

Jan Hudec made changes - 2014-06-24 16:48

Description

Original: Some git processes error out with {{ERROR: Timeout after 10 minutes}} even though longer timeout is configured. It affects the `git checkout` operation itself. The fetch operation is OK. The log says: {noformat} using GIT_SSH to set credentials jenkins key for git  > git fetch --tags --progress git@git.company.com:project +refs/heads/*:refs/remotes/origin/* --prune Checking out Revision 159bc2b21669bc7b5217341fc8de9cd6b48439b2 (origin/dev/jan.hudec/pu)  > git config core.sparsecheckout  > git checkout -f 159bc2b21669bc7b5217341fc8de9cd6b48439b2 ERROR: Timeout after 10 minutes FATAL: Could not checkout null with start point 159bc2b21669bc7b5217341fc8de9cd6b48439b2 {noformat}

New: Some git processes error out with {{ERROR: Timeout after 10 minutes}} even though longer timeout is configured. It affects the `git checkout` operation itself. The fetch operation is OK. The log says: {noformat} using GIT_SSH to set credentials jenkins key for git  > git fetch --tags --progress git@git.company.com:project +refs/heads/*:refs/remotes/origin/* --prune Checking out Revision 159bc2b21669bc7b5217341fc8de9cd6b48439b2 (origin/dev/jan.hudec/pu)  > git config core.sparsecheckout  > git checkout -f 159bc2b21669bc7b5217341fc8de9cd6b48439b2 ERROR: Timeout after 10 minutes FATAL: Could not checkout null with start point 159bc2b21669bc7b5217341fc8de9cd6b48439b2 {noformat} When I manually removed the lock and repeated the checkout operation, it indeed took 11 minutes 15 seconds on the node where it failed.

Jan Hudec made changes - 2014-06-24 16:50

Environment

Original: Windows (8), but I don't think it matters.

New: Windows (8) (the slow disk access probably makes it more likely to manifest)

Jan Hudec made changes - 2014-06-25 09:02

Description	Original: Some git processes error out with {{ERROR: Timeout after 10 minutes}} even though longer timeout is configured. It affects the `git checkout` operation itself. The fetch operation is OK. The log says: {noformat} using GIT_SSH to set credentials jenkins key for git  > git fetch --tags --progress git@git.company.com:project +refs/heads/*:refs/remotes/origin/* --prune Checking out Revision 159bc2b21669bc7b5217341fc8de9cd6b48439b2 (origin/dev/jan.hudec/pu)  > git config core.sparsecheckout  > git checkout -f 159bc2b21669bc7b5217341fc8de9cd6b48439b2 ERROR: Timeout after 10 minutes FATAL: Could not checkout null with start point 159bc2b21669bc7b5217341fc8de9cd6b48439b2 {noformat} When I manually removed the lock and repeated the checkout operation, it indeed took 11 minutes 15 seconds on the node where it failed.	New: Some git processes error out with {{ERROR: Timeout after 10 minutes}} even though longer timeout is configured. It affects the `git checkout` operation itself. The fetch operation is OK. The log says: {noformat} using GIT_SSH to set credentials jenkins key for git  > git fetch --tags --progress git@git.company.com:project +refs/heads/*:refs/remotes/origin/* --prune Checking out Revision 159bc2b21669bc7b5217341fc8de9cd6b48439b2 (origin/dev/jan.hudec/pu)  > git config core.sparsecheckout  > git checkout -f 159bc2b21669bc7b5217341fc8de9cd6b48439b2 ERROR: Timeout after 10 minutes FATAL: Could not checkout null with start point 159bc2b21669bc7b5217341fc8de9cd6b48439b2 {noformat} When I manually removed the lock and repeated the checkout operation, it indeed took 11 minutes 15 seconds on the node where it failed. The global timeout does work, so it's not a blocker anymore. It is, however, rather non-obvious configuration as the {{-Dorg.jenkinsci.plugins.gitclient.Git.timeOut=30}} (or whatever sufficiently large value) option needs to be added to both JVM options of the master _and_ JVM options of all slaves. The master options can only be configured in the servlet container and while the slave options can be configured in node settings (hidden out under "Advanced" button), slaves running as windows service don't take this into account without reinstalling the service.
Priority	Original: Critical [ 2 ]	New: Major [ 3 ]

Jan Hudec made changes - 2014-06-25 09:11

Description

Original: Some git processes error out with {{ERROR: Timeout after 10 minutes}} even though longer timeout is configured. It affects the `git checkout` operation itself. The fetch operation is OK. The log says: {noformat} using GIT_SSH to set credentials jenkins key for git  > git fetch --tags --progress git@git.company.com:project +refs/heads/*:refs/remotes/origin/* --prune Checking out Revision 159bc2b21669bc7b5217341fc8de9cd6b48439b2 (origin/dev/jan.hudec/pu)  > git config core.sparsecheckout  > git checkout -f 159bc2b21669bc7b5217341fc8de9cd6b48439b2 ERROR: Timeout after 10 minutes FATAL: Could not checkout null with start point 159bc2b21669bc7b5217341fc8de9cd6b48439b2 {noformat} When I manually removed the lock and repeated the checkout operation, it indeed took 11 minutes 15 seconds on the node where it failed. The global timeout does work, so it's not a blocker anymore. It is, however, rather non-obvious configuration as the {{-Dorg.jenkinsci.plugins.gitclient.Git.timeOut=30}} (or whatever sufficiently large value) option needs to be added to both JVM options of the master _and_ JVM options of all slaves. The master options can only be configured in the servlet container and while the slave options can be configured in node settings (hidden out under "Advanced" button), slaves running as windows service don't take this into account without reinstalling the service.

New: Some git processes error out with {{ERROR: Timeout after 10 minutes}} even though longer timeout is configured in the job. It affects the `git checkout` operation itself. The fetch operation is OK. The log says: {noformat} using GIT_SSH to set credentials jenkins key for git  > git fetch --tags --progress git@git.company.com:project +refs/heads/*:refs/remotes/origin/* --prune Checking out Revision 159bc2b21669bc7b5217341fc8de9cd6b48439b2 (origin/dev/jan.hudec/pu)  > git config core.sparsecheckout  > git checkout -f 159bc2b21669bc7b5217341fc8de9cd6b48439b2 ERROR: Timeout after 10 minutes FATAL: Could not checkout null with start point 159bc2b21669bc7b5217341fc8de9cd6b48439b2 {noformat} When I manually removed the lock and repeated the checkout operation, it indeed took 11 minutes 15 seconds on the node where it failed. The global timeout does work, so it's not a blocker anymore. It is, however, rather non-obvious configuration as the {{-Dorg.jenkinsci.plugins.gitclient.Git.timeOut=30}} (or whatever sufficiently large value) option needs to be added to both JVM options of the master _and_ JVM options of all slaves. The master options can only be configured in the servlet container and while the slave options can be configured in node settings (hidden out under "Advanced" button), slaves running as windows service don't take this into account without reinstalling the service.

Load more newer history items