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

git-client plugin timeout default is not configurable in a standard manner

    XMLWordPrintable

Details

    Description

      Default timeout value for git operations is 10 mins, which can be modified on a per job basis.

      Having set up many jobs, our repo history has outgrown the 10 minute limit, so many jobs now fail due to timeout.

      Either I should be able to change all jobs using configuration slicing, or I should be able to change the default behaviour of the plugin.

      There is a workaround to set the timeout in the JAVA_ARGS/JAVA_OPTS for the jenkins service start script, and for each slave in the slave configuration, but these make our jenkins server non-portable, which is a requirement.

      Attachments

        Issue Links

          Activity

            apgray Andrew Gray added a comment -

            +1000 if I could. Massive oversight that this is not already there.

            apgray Andrew Gray added a comment - +1000 if I could. Massive oversight that this is not already there.
            markewaite Mark Waite added a comment -

            Pull requests proposing the plugin change and the related user interface for the plugin change are welcomed.

            I guess that if you want to change the default timeout globally, you'd need to add timeout as a globally configured value in the global configuration portion of the git plugin.

            markewaite Mark Waite added a comment - Pull requests proposing the plugin change and the related user interface for the plugin change are welcomed. I guess that if you want to change the default timeout globally, you'd need to add timeout as a globally configured value in the global configuration portion of the git plugin.

            I've created a pull request for this issue
            https://github.com/jenkinsci/git-client-plugin/pull/221

            erik_hakansson Erik Hakansson added a comment - I've created a pull request for this issue https://github.com/jenkinsci/git-client-plugin/pull/221
            orkenstein Real Name added a comment -

            erik_hakansson thanks for your thread.
            Could you please share the code how to modify git timeout now? Assuming I use Docker image.

            orkenstein Real Name added a comment - erik_hakansson thanks for your thread. Could you please share the code how to modify git timeout now? Assuming I use Docker image.
            markewaite Mark Waite added a comment -

            Set org.jenkinsci.plugins.gitclient.Git.timeOut as a JAVA_ARG to the java command line that starts Jenkins

            markewaite Mark Waite added a comment - Set org.jenkinsci.plugins.gitclient.Git.timeOut as a JAVA_ARG to the java command line that starts Jenkins
            orkenstein Real Name added a comment -

            Anybody else wondering:
            ```
            docker run --restart=always -d --env JAVA_OPTS="-Dorg.jenkinsci.plugins.gitclient.Git.timeOut=200" --name jenkins -p 8080:8080 -p 50000:50000 --volumes-from jenkins_bak jenkins
            ```

            orkenstein Real Name added a comment - Anybody else wondering: ``` docker run --restart=always -d --env JAVA_OPTS="-Dorg.jenkinsci.plugins.gitclient.Git.timeOut=200" --name jenkins -p 8080:8080 -p 50000:50000 --volumes-from jenkins_bak jenkins ```
            markewaite Mark Waite added a comment -

            A build of PR221 merged to the git client plugin 2.4.5 base is available. Test reports on the results from that build would be much appreciated.

            Questions to answer while testing:

            • Does the global timeout setting apply to jobs on the master which use default settings for git?
            • Does the global timeout setting apply to jobs on agents which use default settings for git?
            • Is the global timeout setting overridden on master as expected on jobs which specifically set a timeout value?
            • Is the global timeout setting overridden on agents as expected on jobs which specifically set a timeout value?
            • Do git client plugin upgrades behave sensibly from before this change to having this change?
            markewaite Mark Waite added a comment - A build of PR221 merged to the git client plugin 2.4.5 base is available. Test reports on the results from that build would be much appreciated. Questions to answer while testing: Does the global timeout setting apply to jobs on the master which use default settings for git? Does the global timeout setting apply to jobs on agents which use default settings for git? Is the global timeout setting overridden on master as expected on jobs which specifically set a timeout value? Is the global timeout setting overridden on agents as expected on jobs which specifically set a timeout value? Do git client plugin upgrades behave sensibly from before this change to having this change?

            People

              mgaunin Mikael Gaunin
              charlie_ecc Charlie Stott
              Votes:
              9 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated: