[JENKINS-31464] git-client uses proxy from plugins section of jenkins

The git client appears to be using the http proxy settings from the "Manage plugins" section of Jenkins. That proxy is for the master to download plugins, not for SCM clients to access repositories. Slave machines shouldn't require the same access to the internet as the master.

Here you can see that localhost:3128 is being used as a proxy when that slave does not have a proxy listening on port 31218

> /usr/bin/git config --local credential.username frank # timeout=10

> /usr/bin/git config --local credential.helper store --file=/tmp/git6157196107535640953.credentials # timeout=10

Setting http proxy: localhost:3128

> /usr/bin/git -c core.askpass=true fetch --tags --progress https://github.com/frank/fright.git +refs/heads/:refs/remotes/origin/

> /usr/bin/git config --local --remove-section credential # timeout=10

Using environmental variables should be the approach for accessing http/https on the web from a git client.

---
Originally reported by scattym, imported from: git-client uses proxy from plugins section of jenkins

• status: Open
  
• priority: Major
  
• component(s): git-client-plugin
  
• resolution: Unresolved
  
• votes: 19
  
• watchers: 27
  
• imported: 20251211-071809
  

Raw content of original issue

The git client appears to be using the http proxy settings from the "Manage plugins" section of Jenkins. That proxy is for the master to download plugins, not for SCM clients to access repositories. Slave machines shouldn't require the same access to the internet as the master.


Here you can see that localhost:3128 is being used as a proxy when that slave does not have a proxy listening on port 31218

 > /usr/bin/git config --local credential.username frank # timeout=10

 > /usr/bin/git config --local credential.helper store --file=/tmp/git6157196107535640953.credentials # timeout=10

Setting http proxy: localhost:3128

 > /usr/bin/git -c core.askpass=true fetch --tags --progress https://github.com/frank/fright.git +refs/heads/:refs/remotes/origin/

 > /usr/bin/git config --local --remove-section credential # timeout=10


Using environmental variables should be the approach for accessing http/https on the web from a git client.