[JIRA] [git-plugin] (JENKINS-20445) Git plugin timeout is too small

[timknight01@gmail.com (JIRA)]

Tim Knight commented on JENKINS-20445

Re: Git plugin timeout is too small If you add additional behaviours before the operation you can up the timeout for clone and checkout - which has translated to a higher timeout value in my console + Advanced Checkout behaviours + Advanced Clone behaviours Putting any value in timeout overrides the default. Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

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

Mark Waite closed an issue as Fixed

Jenkins / JENKINS-20445

Git plugin timeout is too small

Change By: Mark Waite Status: Resolved Closed

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[cowlinator@gmail.com (JIRA)]

p cowlinator commented on JENKINS-20445

Re: Git plugin timeout is too small The fix mentioned here requires the user to change the "Git plugin section in the job configuration page".  However, this information is not useful for pipeline jobs.  How do you change the timeout value when using the `git()` command in a pipeline?

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

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

Mark Waite commented on JENKINS-20445

Re: Git plugin timeout is too small

p cowlinator you'll need to use the checkout step rather than the git step. The documentation for the git command in pipeline says: The git step is a simplified shorthand for a subset of the more powerful checkout step: {{checkout([$class: 'GitSCM', branches: [[name: '*/master']], userRemoteConfigs: [[url: 'http://git-server/user/repository.git']]])}} NOTE: The checkout step is the preferred SCM checkout method. It provides significantly more functionality than the git step. Use the Pipeline Snippet Generator to generate a sample pipeline script for the checkout step. The checkout step can be used in many cases where the git step cannot be used. Refer to the git plugin documentation for detailed descriptions of options available to the checkout step. For example, the git step does not support: SHA-1 checkout Tag checkout Submodule checkout Sparse checkout Large file checkout (LFS) Reference repositories Branch merges Repository tagging Custom refspecs Timeout configuration Changelog calculation against a non-default reference Stale branch pruning

Add Comment

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

Mark Waite edited a comment on JENKINS-20445

Re: Git plugin timeout is too small

[~cowlinator] you'll need to use the {{checkout step}} rather than the {{git step}}.  The documentation for the {{[git command|https://jenkins.io/doc/pipeline/steps/git/]}} in pipeline says: {quote}The git step is a simplified shorthand for a subset of the more powerful checkout step:

{{ checkout([$class: 'GitSCM', branches: [[name: '*/master']],     userRemoteConfigs: [[url: 'http://git-server/user/repository.git']]]) }}

*NOTE*: The checkout step is the *preferred SCM checkout method*. It provides significantly more functionality than the git step. Use the [Pipeline Snippet Generator|https://jenkins.io/doc/book/pipeline/getting-started/#snippet-generator] to generate a sample pipeline script for the checkout step.

The checkout step can be used in many cases where the git step cannot be used. Refer to the git plugin documentation for detailed descriptions of options available to the checkout step. For example, the git step does not support:

* SHA-1 checkout * Tag checkout * Submodule checkout * Sparse checkout * Large file checkout (LFS) * Reference repositories * Branch merges * Repository tagging * Custom refspecs * *Timeout configuration* * Changelog calculation against a non-default reference * Stale branch pruning{quote}

Add Comment