Git plugin timeout is too small

Details

Description

Right now git plugin timeouts always after 10 minutes, regardless if it receives any response from git.
First of all 10 minute timeout is to small, it should be more like 30 minutes or 1 hour.
More over there is no mention how to change this timeout to different value.

Activity

In the job configuration page under the Git plugin section, there is a drop-down list "Add". Within that dropdown list there is a selection "Advanced clone behaviours". When you add the advanced clone behaviors, you'll see a field for "Timeout (in minutes) for clone and fetch operation".

Mark Waite
added a comment - 2014-02-25 20:13 In the job configuration page under the Git plugin section, there is a drop-down list "Add". Within that dropdown list there is a selection "Advanced clone behaviours". When you add the advanced clone behaviors, you'll see a field for "Timeout (in minutes) for clone and fetch operation".

Tim Knight
added a comment - 2015-08-04 10:49 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.

It is not enough to say "the same issue occurring". You'll need to provide much more context than "same issue occurring". What have you tried? What is the context where timeouts are not behaving as you expect? What is the log content when the timeout does not behave as you expect? What job type are you using?

Please gather those details and submit a new bug report, rather than reopening this report.

There are many, many users that are successfully using extended timeouts to clone and checkout large repositories. I've presented talks at Jenkins World 2016, Jenkins World 2017,at a 2016 online meetup and at a 2017 online meetup that describe techniques to better manage large repositories. All of those talks depend on adjusting timeout values as needed, and they work.

Mark Waite
added a comment - 2017-10-12 11:29 - edited Vadivel Natarajan the bug was fixed over 2 years ago. and is as described by Tim Knight in the comment above your comment that you're reopening the bug.
It is not enough to say "the same issue occurring". You'll need to provide much more context than "same issue occurring". What have you tried? What is the context where timeouts are not behaving as you expect? What is the log content when the timeout does not behave as you expect? What job type are you using?
Please gather those details and submit a new bug report, rather than reopening this report.
There are many, many users that are successfully using extended timeouts to clone and checkout large repositories. I've presented talks at Jenkins World 2016 , Jenkins World 2017 ,at a 2016 online meetup and at a 2017 online meetup that describe techniques to better manage large repositories. All of those talks depend on adjusting timeout values as needed, and they work.
In addition to those resources, CloudBees support has provided detailed instructions for configuring a reference repository to speed clone operations.