-
New Feature
-
Resolution: Unresolved
-
Major
-
None
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.
- is related to
-
JENKINS-73204 The git client plugin uses Jenkins proxy by default ( Setting http proxy: )
-
- Closed
-
I am seeing this issue with Pipelines. Has anybody figured a way around this? I cannot run a pipeline with git on my repository which needs to be accessed via proxy – it works fine if I run a manual Pipeline.
All ways to set environment variables on Jenkins also haven't helped as it seems that this ultimately gets overwritten by the Git plugin no matter what I do.