[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Andreas Mandel commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins We also have different proxy settings on the master and agents. Fortunately a local .gitconfig on the build node has precedence over the setting from the master. So we distribute a /home/jenkins/.gitconfig file with the following content to the build nodes: /home/jenkins/.gitconfig [http "https://git.example.com"] proxy = http://proxy.example.com:3128 [http "https://dev.example.com"] proxy = http://proxy2.example.com:3128 Jenkins still logs Setting http proxy: proxy.masteronly.example.com:3128 during the build - but git selects the proxy from the local .gitconfig. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166331.1447113678000.6303.1566319321120%40Atlassian.JIRA.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Yusuke Ohashi edited a comment on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Hello,I also had this issue, and solved by modifying git-plugin only.Here is my change. [ https://github.com/junkpiano/git-plugin/commit/ 634f8087749909a53c5b3f3db7ffd96c4af84b24] 7f86f4113bd9813ccfb2e684ecfcbea4277cc458 In my environment, master and slave machines are located in different network zones. All machines can connect with each others. Some machines needs proxy to access external contents but the others don't. So I introduced environmental variable to toggle proxy on/off on node. This gives you flexible proxy setting on the fly.There might be something I missed, so your feedbacks are appreciated.Thanks. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Yusuke Ohashi commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Hello, I also had this issue, and solved by modifying git-plugin only. Here is my change. https://github.com/junkpiano/git-plugin/commit/634f8087749909a53c5b3f3db7ffd96c4af84b24 In my environment, master and slave machines are located in different network zones. All machines can connect with each others. Some machines needs proxy to access external contents but the others don't. So I introduced environmental variable to toggle proxy on/off on node. This gives you flexible proxy setting on the fly. There might be something I missed, so your feedbacks are appreciated. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Christian Schneider commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins withEnv does not help. I think, because "These are available to any external processes spawned within that scope." (and they are available to the external processes already). Even setting env.http_proxy directly in the pipeline does not help. The question would probably be which EnvVars is passed to CliGitAPIImpl in the first place. But I can't afford the time for setting up a complete debug environment for this. Seems I will need to checkout via command line without using the git plugin. 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark edited a comment on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins [~ccschneidr]Oh good. That's a step closer... I haven't used pipelines yet. I was actually just looking into the concept a few days ago. I don't know if it's of any help to you, but a quick search shows up that you can set envars inside of your pipeline definition. Of course not having used them I don't know if it's relevant for your situation:[http://stackoverflow.com/questions/39171341/load-file-with-environment-variables-jenkins-pipeline]Note specifically the comment about using "withEnv" being the correct way to handle environmental variables within a scope .Let me know how you go as I will have the same problem as you soon! 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark edited a comment on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins [~ccschneidr]Oh good. That's a step closer... I haven't used pipelines yet. I was actually just looking into the concept a few days ago. I don't know if it's of any help to you, but a quick search shows up that you can set envars inside of your pipeline definition. Of course not having used them I don't know if it's relevant for your situation:[http://stackoverflow.com/questions/39171341/load-file-with-environment-variables-jenkins-pipeline] Note specifically the comment about using "withEnv". Let me know how you go as I will have the same problem as you soon! 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Christian Schneider Oh good. That's a step closer... I haven't used pipelines yet. I was actually just looking into the concept a few days ago. I don't know if it's of any help to you, but a quick search shows up that you can set envars inside of your pipeline definition. Of course not having used them I don't know if it's relevant for your situation: http://stackoverflow.com/questions/39171341/load-file-with-environment-variables-jenkins-pipeline Let me know how you go as I will have the same problem as you soon! 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Christian Schneider commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Well, yes, it is related to pipelines: Using the old school checkout of a single git repository I get "Leaving http_proxy set to [...]" and it works. Unfortunately that does not help me with my pipelines :/ 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title
Christian Schneider edited a comment 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:{code:java}node('linux') {sh 'env'println "Node env:"println env.getEnvironment()println "EnvVars:"println new hudson.EnvVars()checkout([something from github])}{code}Using your new plugin version (and Jenkins ver. 2.32.2) it prints the following:{noformat}Running on linux1 in /home/buildchain/work/buildnode/workspace/test[Pipeline] {[Pipeline] sh[test] Running shell script+ env[...]http_proxy=http://[correct.proxy].[...].de:8080https_proxy=http://[correct.proxy].[...].de:8080[...]no_proxy=[...].de,[...].com[...][Pipeline] echoNode env:[Pipeline] echo{BUILD_DISPLAY_NAME=#7, BUILD_ID=7, BUILD_NUMBER=7, BUILD_TAG=jenkins-[...]-test [...]}[Pipeline] echoEnvVars:[Pipeline] echo{}[Pipeline] checkoutCloning the remote Git repositoryCloning repository https://github.com/collaborationFactory/[...].git > git init /home/buildchain/work/buildnode/workspace/[...]/test/main # timeout=10Fetching upstream changes from https://github.com/collaborationFactory/[...].git > git --version # timeout=10using GIT_ASKPASS to set credentials [...] GitHubCredentialsSetting http proxy: [wrong.proxy].[...].de:8080Checking if proxy already set in env.http_proxy in env is set to Setting http_proxy to be http://[ correct wrong .proxy].[...].de:8080https_proxy in env is set to Setting https_proxy to be http://[ correct wrong .proxy].[...].de:8080 > git fetch --tags --progress https://github.com/collaborationFactory/[...].git +refs/heads/*:refs/remotes/origin/* # timeout=240ERROR: 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{noformat}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. P.S. sorry messed up the proxies while anonymyzing their names
Add Comment
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title
Christian Schneider edited a comment 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:{code:java}node('linux') {sh 'env'println "Node env:"println env.getEnvironment()println "EnvVars:"println new hudson.EnvVars()checkout([something from github])}{code}Using your new plugin version (and Jenkins ver. 2.32.2) it prints the following:{noformat}Running on linux1 in /home/buildchain/work/buildnode/workspace/test[Pipeline] {[Pipeline] sh[test] Running shell script+ env[...]http_proxy=http://[correct.proxy].[...].de:8080https_proxy=http://[correct.proxy].[...].de:8080[...]no_proxy=[...].de,[...].com[...][Pipeline] echoNode env:[Pipeline] echo{BUILD_DISPLAY_NAME=#7, BUILD_ID=7, BUILD_NUMBER=7, BUILD_TAG=jenkins-[...]-test [...]}[Pipeline] echoEnvVars:[Pipeline] echo{}[Pipeline] checkoutCloning the remote Git repositoryCloning repository https://github.com/collaborationFactory/[...].git > git init /home/buildchain/work/buildnode/workspace/[...]/test/main # timeout=10Fetching upstream changes from https://github.com/collaborationFactory/[...].git > git --version # timeout=10using GIT_ASKPASS to set credentials [...] GitHubCredentialsSetting http proxy: [wrong.proxy].[...].de:8080Checking if proxy already set in env.http_proxy in env is set to Setting http_proxy to be http://[wrong.proxy].[...].de:8080https_proxy in env is set to Setting https_proxy to be http://[wrong.proxy].[...].de:8080 > git fetch --tags --progress https://github.com/collaborationFactory/[...].git +refs/heads/*:refs/remotes/origin/* # timeout=240ERROR: 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{noformat}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. P.S. sorry messed up the proxies while anonymyzing their names
Add Comment
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
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
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark edited a comment on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins [~ccschneidr] The EnvVars must work. I just recompiled the latest git-client-plugin (2.3.0) with the change and I have just got a heap of my build servers back :)I see the following lines in the console output:Setting http proxy: 10.1.1.1:3128Leaving http_proxy set to http://192.168.1.1:3128Leaving https_proxy set to http://192.168.1.1:3128If you are setting the env variables in the same place this would work.These are the only things I can think of:1. Using HTTP_PROXY instead of http_proxy (really I should be checking both) 2. Environmental variables are being set at a later point3. Plugin doesn't contain the patch or didn't upload properly4. git client you are using doesn't support proxy behaviour (although, if you are not seeing the Leaving lines then this is unlikely the problem yet)I've added some logging just before the conditional. Give this a try and check the output at the top:https://drive.google.com/drive/folders/0ByO3I08lkskfSUtYZzVpMGhFTUE?usp=sharingIt will print the values of http_proxy and https_proxy from the environment before entering the new conditional logic.It's based off of the latest release. Hopefully that is compatible with the version of jenkins you are using. 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
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark edited a comment on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins [~ccschneidr] The EnvVars must work. I just recompiled the latest git-client-plugin (2.3.0) with the change and I have just got a heap of my build servers back :)I see the following lines in the console output:Setting http proxy: 10.1.1.1:3128Leaving http_proxy set to http://192.168.1.1:3128Leaving https_proxy set to http://192.168.1.1:3128If you are setting the env variables in the same place this would work.These are the only things I can think of:1. Using HTTP_PROXY instead of http_proxy2. Environmental variables are being set at a later point3. Plugin doesn't contain the patch or didn't upload properly4. git client you are using doesn't support proxy behaviour (although, if you are not seeing the Leaving lines then this is unlikely the problem yet)I've added some logging just before the conditional. Give this a try and check the output at the top:https://drive.google.com/ file drive / d folders / 0ByO3I08lkskfTUhZMjRPeVhoTms/view 0ByO3I08lkskfSUtYZzVpMGhFTUE ?usp=sharingIt will print the values of http_proxy and https_proxy from the environment before entering the new conditional logic.It's based off of the latest release. Hopefully that is compatible with the version of jenkins you are using. 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,
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark edited a comment on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins [~ccschneidr] The EnvVars must work. I just recompiled the latest git-client-plugin (2.3.0) with the change and I have just got a heap of my build servers back :)I see the following lines in the console output:Setting http proxy: 10.1.1.1:3128Leaving http_proxy set to http://192.168.1.1:3128Leaving https_proxy set to http://192.168.1.1:3128If you are setting the env variables in the same place this would work.These are the only things I can think of:1. Using HTTP_PROXY instead of http_proxy2. Environmental variables are being set at a later point3. Plugin doesn't contain the patch or didn't upload properly4. git client you are using doesn't support proxy behaviour (although, if you are not seeing the Leaving lines then this is unlikely the problem yet)I've added some logging just before the conditional. Give this a try and check the output at the top:https://drive.google.com/ open file/d/0ByO3I08lkskfTUhZMjRPeVhoTms/view ? id usp = 0ByO3I08lkskfTUhZMjRPeVhoTms sharing It will print the values of http_proxy and https_proxy from the environment before entering the new conditional logic.It's based off of the latest release. Hopefully that is compatible with the version of jenkins you are using. 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
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark edited a comment on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins [~ccschneidr] The EnvVars must work. I just recompiled the latest git-client-plugin (2.3.0) with the change and I have just got a heap of my build servers back :)I see the following lines in the console output:Setting http proxy: 10.1.1.1:3128Leaving http_proxy set to http://192.168.1.1:3128Leaving https_proxy set to http://192.168.1.1:3128If you are setting the env variables in the same place this would work.These are the only things I can think of:1. Using HTTP_PROXY instead of http_proxy2. Environmental variables are being set at a later point3. Plugin doesn't contain the patch or didn't upload properly4. git client you are using doesn't support proxy behaviour (although, if you are not seeing the Leaving lines then this is unlikely the problem yet)I've added some logging just before the conditional. Give this a try and check the output at the top:https://drive.google.com/open?id= 0ByO3I08lkskfSUtYZzVpMGhFTUE 0ByO3I08lkskfTUhZMjRPeVhoTms It will print the values of http_proxy and https_proxy from the environment before entering the new conditional logic.It's based off of the latest release. Hopefully that is compatible with the version of jenkins you are using. 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
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark edited a comment on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins [~ccschneidr] The EnvVars must work. I just recompiled the latest git-client-plugin (2.3.0) with the change and I have just got a heap of my build servers back :)I see the following lines in the console output:Setting http proxy: 10.1.1.1:3128Leaving http_proxy set to http://192.168.1.1:3128Leaving https_proxy set to http://192.168.1.1:3128If you are setting the env variables in the same place this would work.These are the only things I can think of:1. Using HTTP_PROXY instead of http_proxy2. Environmental variables are being set at a later point3. Plugin doesn't contain the patch or didn't upload properly4. git client you are using doesn't support proxy behaviour (although, if you are not seeing the Leaving lines then this is unlikely the problem yet) Do you have a way I can send you 've added some logging just before the git-client conditional . hpi file Give this a try and check the output at the top:https://drive.google.com/open ? id=0ByO3I08lkskfSUtYZzVpMGhFTUE It will print the values of http_proxy and https_proxy from the environment before entering the new conditional logic.It's based off of the latest release. Hopefully that is compatible with the version of jenkins you are using. 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,
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark edited a comment on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins [~ccschneidr] The EnvVars must work. I just recompiled the latest git-client-plugin (2.3.0) with the change and I have just got a heap of my build servers back :)I see the following lines in the console output:Setting http proxy: 10. 108 1 . 189 1 .1:3128Leaving http_proxy set to http:// 10 192 . 11 168 . 69 1 . 105 1 :3128Leaving https_proxy set to http:// 10 192 . 11 168 . 69 1 . 105 1 :3128If you are setting the env variables in the same place this would work.These are the only things I can think of:1. Using HTTP_PROXY instead of http_proxy2. Environmental variables are being set at a later point3. Plugin doesn't contain the patch or didn't upload properly4. git client you are using doesn't support proxy behaviour (although, if you are not seeing the Leaving lines then this is unlikely the problem yet)Do you have a way I can send you the git-client.hpi file? 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Christian Schneider The EnvVars must work. I just recompiled the latest git-client-plugin (2.3.0) with the change and I have just got a heap of my build servers back I see the following lines in the console output: Setting http proxy: 10.108.189.1:3128 Leaving http_proxy set to http://10.11.69.105:3128 Leaving https_proxy set to http://10.11.69.105:3128 If you are setting the env variables in the same place this would work. These are the only things I can think of: 1. Using HTTP_PROXY instead of http_proxy 2. Environmental variables are being set at a later point 3. Plugin doesn't contain the patch or didn't upload properly 4. git client you are using doesn't support proxy behaviour (although, if you are not seeing the Leaving lines then this is unlikely the problem yet) Do you have a way I can send you the git-client.hpi file? 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title
Christian Schneider commented on JENKINS-31464
Re: git-client uses proxy from plugins section of jenkins
Hey Matt, thanks for looking into it. For me it prints the "Setting http_proxy to be ..." sentences. And yes, my setup sounds like yours: http_proxy (and https_proxy and no_proxy) are set as environment variables outside of the build node process. So calling "sh 'env'" in a pipeline script prints the desired proxy settings. In contrast to that, "env.getEnvironment()['http_proxy']" is null in a pipeline. And while env.getEnvironment() contains at least some other properties, new EnvVars() is completely empty (thus new EnvVars().get("http_proxy", "") is ""). So, yes, the "env = new EnvVars()" line does not originate from your patch. Still it always creates an empty EnvVars, doesn't it?
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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title
Matt Clark edited a comment on JENKINS-31464
Re: git-client uses proxy from plugins section of jenkins
[~ccschneidr][~markewaite] I just checked and in November we upgraded jenkins which included git-client-plugin 2.1.0 which did not have my patch. No reason to think there is anything wrong with the code then.Christian, when you look at the console output. Do you see the lines "Leaving http_proxy set to X".How are you setting http_proxy and https_proxy?The following is in place for our build user:{code :bash }[builduser@somemachine-vm2 ~]$ cat .profile export http_proxy=http://192.168.1.1:3128export https_proxy=http://192.168.1.1:3128{code}
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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title
Matt Clark edited a comment on JENKINS-31464
Re: git-client uses proxy from plugins section of jenkins
[~ccschneidr][~markewaite] I just checked and in November we upgraded jenkins which included git-client-plugin 2.1.0 which did not have my patch. No reason to think there is anything wrong with the code then.Christian, when you look at the console output. Do you see the lines "Leaving http_proxy set to X".How are you setting http_proxy and https_proxy? The following is in place for our build user:{code:bash}[builduser@somemachine-vm2 ~]$ cat .profile export http_proxy=http://192.168.1.1:3128export https_proxy=http://192.168.1.1:3128{code}
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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Christian SchneiderMark Waite I just checked and in November we upgraded jenkins which included git-client-plugin 2.1.0 which did not have my patch. No reason to think there is anything wrong with the code then. Christian, when you look at the console output. Do you see the lines "Leaving http_proxy set to X". How are you setting http_proxy and https_proxy? 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark edited a comment on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins [~ccschneidr][~markewaite] I can confirm this workaround stopped working on November 28th 2016.That's around the same time as we did an upgrade to Jenkins. The workaround falls back to current behaviour so that's what you are seeing at the moment. 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Christian SchneiderMark Waite I can confirm this workaround stopped working on November 28th 2016. That's around the same time as we did an upgrade to Jenkins. 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Christian Schneider commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Thanks. Tested it, but it does not work 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Mark Waite commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Christian Schneider I've built a copy of the tip of the git client plugin master branch with this pull request included and placed it on my google drive. I've done no testing myself of that change, though I did briefly review the source code of the change. 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Christian Schneider commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Any chance to get this PR included? I'm hesitating to build Jenkins on my own. But if someone can easily build with this PR, I'm happy to test and report back. 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Christian Schneider edited a comment on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins The There does not even seem to be a possible workaround to set the proxy per node. For me this forbids using client in other subnets (where the only option to checkout is using a different proxy). 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Christian Schneider updated an issue Jenkins / JENKINS-31464 git-client uses proxy from plugins section of jenkins Change By: Christian Schneider Priority: Minor Major 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Christian Schneider commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins The does not even seem to be a possible workaround to set the proxy per node. For me this forbids using client in other subnets (where the only option to checkout is using a different proxy). 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Mark R commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Ended up hitting this today. It took several hours to debug and come to the root cause. 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Mark Waite commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Not resolved. The pull request is still open. You could build your own copy of the plugin which includes the master branch and the pull request. That would give you the fix and would provide an additional tester to declare if the change is working well for you. Proxy configuration changes are especially scary because they risk breaking users very badly. They are difficult to test due to the many different forms of proxying. 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.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Pratith Kanagaraj commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Was this resolved? Because I am still facing the issue 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.
