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

[christian07.schnei...@conti.de (JIRA)]

Title: Message Title

Christian Schneider commented on JENKINS-31464   Re: git-client uses proxy from plugins section of jenkins Maybe this is related to pipelines? Will EnvVars behave differently there? I'm using the following pipeline script to test it: node('linux') { sh 'env' println "Node env:" println env.getEnvironment() println "EnvVars:" println new hudson.EnvVars() checkout([something from github]) } Using your new plugin version (and Jenkins ver. 2.32.2) it prints the following: Running on linux1 in /home/buildchain/work/buildnode/workspace/test [Pipeline] { [Pipeline] sh [test] Running shell script + env [...] http_proxy=http://[correct.proxy].[...].de:8080 https_proxy=http://[correct.proxy].[...].de:8080 [...] no_proxy=[...].de,[...].com [...] [Pipeline] echo Node env: [Pipeline] echo {BUILD_DISPLAY_NAME=#7, BUILD_ID=7, BUILD_NUMBER=7, BUILD_TAG=jenkins-[...]-test [...]} [Pipeline] echo EnvVars: [Pipeline] echo {} [Pipeline] checkout Cloning the remote Git repository Cloning repository https://github.com/collaborationFactory/[...].git > git init /home/buildchain/work/buildnode/workspace/[...]/test/main # timeout=10 Fetching upstream changes from https://github.com/collaborationFactory/[...].git > git --version # timeout=10 using GIT_ASKPASS to set credentials [...] GitHubCredentials Setting http proxy: [wrong.proxy].[...].de:8080 Checking if proxy already set in env. http_proxy in env is set to Setting http_proxy to be http://[correct.proxy].[...].de:8080 https_proxy in env is set to Setting https_proxy to be http://[correct.proxy].[...].de:8080 > git fetch --tags --progress https://github.com/collaborationFactory/[...].git +refs/heads/*:refs/remotes/origin/* # timeout=240 ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress https://github.com/collaborationFactory/[...].git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: unable to access 'https://github.com/[...].git/': Received HTTP code 407 from proxy after CONNECT So the environment variables are set for the process of the build node. But they are not reflected inside groovy. I guess they would need to be loaded explicitly for the current build node. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.