[JENKINS-23476] git-client plugin timeout default is not configurable in a standard manner

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.

---
Originally reported by charlie_ecc, imported from: git-client plugin timeout default is not configurable in a standard manner

• assignee: mgaunin
  
• status: Open
  
• priority: Major
  
• component(s): configurationslicing-plugin, git-client-plugin
  
• label(s): configuration, git, plugin, slicing
  
• resolution: Unresolved
  
• votes: 9
  
• watchers: 12
  
• imported: 20251211-071809
  

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.

• environment: All (tested in Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.57-3+deb7u1)