Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39111

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

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: git-plugin
    • Labels:
    • Environment:
      Jenkins 2.7.4, Git plugin 2.6.0
    • Similar Issues:

      Description

      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!

        Attachments

          Issue Links

            Activity

            There are no comments yet on this issue.

              People

              • Assignee:
                Unassigned
                Reporter:
                hushp1pt Tony Wallace
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: