• Type: Improvement
• Resolution: Unresolved
• Priority: Major
• Component/s: parameterized-remote-trigger-plugin
• Labels:

  None

[JENKINS-23895] does not respect http_proxy variables

Bryan Taylor created issue - 2014-07-21 00:42

Bryan Taylor made changes - 2014-07-21 00:44

Component/s		New: parameterized-remote-trigger [ 18159 ]
Component/s	Original: plugin [ 15491 ]
Description	Original: (sorry if I used the wrong component!) moved from one I created in github: https://github.com/morficus/Parameterized-Remote-Trigger-Plugin/issues/3 Hi! Thanks for the great plugin. We have a remote job that currently works with curl, using env var http_proxy. We can't get the build to work using the plugin, so I was assuming it is because it does not use http_proxy. I'm mediocre at java, but I will try to submit a patch. I just wanted to put this out there in case others are having the same issue. morficus commented 21 hours ago Good find. You're actually the first to report such an issue, but you're right. The plugin doesn't do anything special to use a proxy when connecting to the remote server. This should be a relatively easy fix once I figure out how to access Jenkins' environment variables :-p Oh, and for the record: the "official" bug tracker lives here: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Remote+Trigger+Plugin (scroll all the way to the bottom)	New: moved from one I created in github: https://github.com/morficus/Parameterized-Remote-Trigger-Plugin/issues/3 Hi! Thanks for the great plugin. We have a remote job that currently works with curl, using env var http_proxy. We can't get the build to work using the plugin, so I was assuming it is because it does not use http_proxy. I'm mediocre at java, but I will try to submit a patch. I just wanted to put this out there in case others are having the same issue. morficus commented 21 hours ago Good find. You're actually the first to report such an issue, but you're right. The plugin doesn't do anything special to use a proxy when connecting to the remote server. This should be a relatively easy fix once I figure out how to access Jenkins' environment variables :-p Oh, and for the record: the "official" bug tracker lives here: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Remote+Trigger+Plugin (scroll all the way to the bottom)

R. Tyler Croy made changes - 2016-07-25 23:51

Workflow

Original: JNJira [ 156760 ]

New: JNJira + In-Review [ 179380 ]