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

Git timeout setting does not work for checkout

    XMLWordPrintable

    Details

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

      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

            Activity

            bulb Jan Hudec created issue -
            bulb Jan Hudec made changes -
            Field Original Value New Value
            Link This issue is related to JENKINS-20445 [ JENKINS-20445 ]
            bulb Jan Hudec made changes -
            Link This issue is related to JENKINS-11286 [ JENKINS-11286 ]
            markewaite Mark Waite made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Cannot Reproduce [ 5 ]
            markewaite Mark Waite made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            bulb Jan Hudec made changes -
            Resolution Cannot Reproduce [ 5 ]
            Status Closed [ 6 ] Reopened [ 4 ]
            bulb Jan Hudec made changes -
            Summary Matrix jobs don't honor git timeout setting Git timeout setting does not work for checkout
            Labels git matrix plugin configuration git plugin
            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.
            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}
            bulb Jan Hudec made changes -
            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}
            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.
            bulb Jan Hudec made changes -
            Environment Windows (8), but I don't think it matters. Windows (8) (the slow disk access probably makes it more likely to manifest)
            bulb Jan Hudec made changes -
            Priority Critical [ 2 ] Major [ 3 ]
            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.
            bulb Jan Hudec made changes -
            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.
            markewaite Mark Waite made changes -
            Link This issue duplicates JENKINS-20387 [ JENKINS-20387 ]
            markewaite Mark Waite made changes -
            Assignee Nicolas De Loof [ ndeloof ] Mark Waite [ markewaite ]
            markewaite Mark Waite made changes -
            Status Reopened [ 4 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            markewaite Mark Waite made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            manschwetus Florian Manschwetus made changes -
            Resolution Fixed [ 1 ]
            Status Closed [ 6 ] Reopened [ 4 ]
            markewaite Mark Waite made changes -
            Assignee Mark Waite [ markewaite ]
            markewaite Mark Waite made changes -
            Assignee Mark Waite [ markewaite ]
            markewaite Mark Waite made changes -
            Status Reopened [ 4 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 154649 ] JNJira + In-Review [ 194978 ]
            markewaite Mark Waite made changes -
            Resolution Fixed [ 1 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            markewaite Mark Waite made changes -
            Link This issue duplicates JENKINS-37185 [ JENKINS-37185 ]
            markewaite Mark Waite made changes -
            Status Reopened [ 4 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            mcabalaji Balaji Santhanam made changes -
            Resolution Fixed [ 1 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            mcabalaji Balaji Santhanam made changes -
            Status Reopened [ 4 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            mcabalaji Balaji Santhanam made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            vadivel Vadivel Natarajan made changes -
            Resolution Fixed [ 1 ]
            Status Closed [ 6 ] Reopened [ 4 ]
            markewaite Mark Waite made changes -
            Status Reopened [ 4 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            vadivel Vadivel Natarajan made changes -
            Comment [ I have tried the solution which you gave. But still, am facing an issue.  ]

              People

              • Assignee:
                markewaite Mark Waite
                Reporter:
                bulb Jan Hudec
              • Votes:
                1 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: