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

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Component/s: git-plugin
Labels:
- configuration
- git
- plugin
Environment:
Windows (8) (the slow disk access probably makes it more likely to manifest)

Similar Issues:

Show

Description

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:

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

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.

Attachments

Issue Links

duplicates

JENKINS-20387 git submodule update timeout value should be configurable per job

Closed

JENKINS-37185 Checkout timeout is not honored when used with local branch parameter

Closed

is related to

JENKINS-11286 Git plugin does not timeout

Closed

JENKINS-20445 Git plugin timeout is too small

Closed

Activity

Ascending order - Click to sort in descending order

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

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

Field	Original Value	New Value
Link		This issue is related to ~~JENKINS-20445~~ [ ~~JENKINS-20445~~ ]

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

Link

This issue is related to ~~JENKINS-11286~~ [ ~~JENKINS-11286~~ ]

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

Resolution		Cannot Reproduce [ 5 ]
Status	Open [ 1 ]	Resolved [ 5 ]

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

Status

Resolved [ 5 ]

Closed [ 6 ]

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

Resolution	Cannot Reproduce [ 5 ]
Status	Closed [ 6 ]	Reopened [ 4 ]

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

Description	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.	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	Windows (8), but I don't think it matters. Unfortunately our MacOS builder is currently broken, so I can't test there.	Windows (8), but I don't think it matters.
Labels	git matrix plugin	configuration git plugin
Summary	Matrix jobs don't honor git timeout setting	Git timeout setting does not work for checkout

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

Description

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

Environment

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

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

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

Description	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.	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	Critical [ 2 ]	Major [ 3 ]

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

Description

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.

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.

Mark Waite made changes - 2014-06-27 00:01

Link

This issue duplicates ~~JENKINS-20387~~ [ ~~JENKINS-20387~~ ]

Mark Waite made changes - 2014-07-28 04:21

Assignee

Nicolas De Loof [ ndeloof ]

Mark Waite [ markewaite ]

Mark Waite made changes - 2014-07-31 12:58

Resolution		Fixed [ 1 ]
Status	Reopened [ 4 ]	Resolved [ 5 ]

Mark Waite made changes - 2014-07-31 12:59

Status

Resolved [ 5 ]

Closed [ 6 ]

Florian Manschwetus made changes - 2016-07-07 11:43

Resolution	Fixed [ 1 ]
Status	Closed [ 6 ]	Reopened [ 4 ]

Mark Waite made changes - 2016-07-07 12:40

Assignee

Mark Waite [ markewaite ]

Mark Waite made changes - 2016-07-18 11:36

Assignee

Mark Waite [ markewaite ]

Mark Waite made changes - 2016-07-20 20:48

Resolution		Fixed [ 1 ]
Status	Reopened [ 4 ]	Resolved [ 5 ]

R. Tyler Croy made changes - 2016-07-25 23:56

Workflow

JNJira [ 154649 ]

JNJira + In-Review [ 194978 ]

Mark Waite made changes - 2016-08-05 11:54

Resolution	Fixed [ 1 ]
Status	Resolved [ 5 ]	Reopened [ 4 ]

Mark Waite made changes - 2016-08-05 13:11

Link

This issue duplicates ~~JENKINS-37185~~ [ ~~JENKINS-37185~~ ]

Mark Waite made changes - 2016-08-20 20:22

Resolution		Fixed [ 1 ]
Status	Reopened [ 4 ]	Resolved [ 5 ]

Balaji Santhanam made changes - 2017-01-03 21:48

Resolution	Fixed [ 1 ]
Status	Resolved [ 5 ]	Reopened [ 4 ]

Balaji Santhanam made changes - 2017-01-04 15:14

Resolution		Fixed [ 1 ]
Status	Reopened [ 4 ]	Resolved [ 5 ]

Balaji Santhanam made changes - 2017-01-04 15:14

Status

Resolved [ 5 ]

Closed [ 6 ]

Vadivel Natarajan made changes - 2017-10-12 10:54

Resolution	Fixed [ 1 ]
Status	Closed [ 6 ]	Reopened [ 4 ]

Mark Waite made changes - 2017-10-12 11:30

Resolution		Fixed [ 1 ]
Status	Reopened [ 4 ]	Resolved [ 5 ]

Vadivel Natarajan made changes - 2017-10-13 10:06

Comment

[ I have tried the solution which you gave. But still, am facing an issue. ]

Mark Waite made changes - 2019-10-23 01:28

Status

Resolved [ 5 ]

Closed [ 6 ]

People

Assignee:: Mark Waite

Reporter:: Jan Hudec

Votes:: 1 Vote for this issue

Watchers:: 13 Start watching this issue

Dates

Created:: 2014-04-09 12:55

Updated:: 2019-10-23 01:28

Resolved:: 2017-10-12 11:30