[JIRA] (JENKINS-39111) Git client timeout for checkout operation should be applied to git clean

2 views
Skip to first unread message

anthonylee.wallace@gmail.com (JIRA)

unread,
Oct 19, 2016, 10:42:03 AM10/19/16
to jenkinsc...@googlegroups.com
Tony Wallace created an issue
 
Jenkins / Bug JENKINS-39111
Git client timeout for checkout operation should be applied to git clean
Issue Type: Bug Bug
Assignee: Mark Waite
Components: git-plugin
Created: 2016/Oct/19 2:41 PM
Environment: Jenkins 2.7.4, Git plugin 2.6.0
Labels: git
Priority: Minor Minor
Reporter: Tony Wallace

Git client timeout for checkout operation should be applied to git clean

Similar to JENKINS-29164, except this request is for "git clean" operations.

A Linux build slave with Jenkins workspace on a remote (NFS) file system had frequent build failures due to git client timeout.

We increased the configured git client time limit from 10 to 20, in both "Advanced checkout behaviours" and "Advanced clone behaviors".

The git client timeout error occured less often, but it still happens occasionally in "git clean" (we use the "Clean After Checkout" Git behaviour). The console log shows that git clean gets a timeout value of 10 (the default), not 20 (our configured value).

If the user-specified git client timeout value is applied to git checkout, then it should also be applied to git clean. Both git operations are vulnerable to file system slowdowns.

Thanks!

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

mark.earl.waite@gmail.com (JIRA)

unread,
Oct 19, 2016, 12:16:01 PM10/19/16
to jenkinsc...@googlegroups.com

mark.earl.waite@gmail.com (JIRA)

unread,
Jul 24, 2019, 9:20:02 AM7/24/19
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
 
Jenkins / New Feature JENKINS-39111
Change By: Mark Waite
Issue Type: Bug New Feature
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages