By default, Git Plugin uses the native git CLI. Therefore, if you run the command on the Agent using the same git as Jenkins configure to use, it will be written in a right config file and should be picked up from Jenkins.
Users of the most recent version of Windows 10 can also set a registry key that will enable long paths across the entire system (rather than just configuring core.longpaths for git).
There is also a system-wide configuration which can be set for git by a user running as administrator. Use the "--system" argument instead of "--global".
Comments
3 comments
Where should the above setting be configured? Which location does git plugin from Jenkins read to get the config settings ?
Hi Utp Team,
By default, Git Plugin uses the native git CLI. Therefore, if you run the command on the Agent using the same git as Jenkins configure to use, it will be written in a right config file and should be picked up from Jenkins.
Users of the most recent version of Windows 10 can also set a registry key that will enable long paths across the entire system (rather than just configuring core.longpaths for git).
There is also a system-wide configuration which can be set for git by a user running as administrator. Use the "--system" argument instead of "--global".
Please sign in to leave a comment.