Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-23895

does not respect http_proxy variables

    XMLWordPrintable

Details

    Description

      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)

      Attachments

        Activity

          This one is blocking me as well
          I'd love to use the plugin, but I'm within an environment where I have to go through proxies between the jenkins hosts.

          timothy_clarke Timothy Clarke added a comment - This one is blocking me as well I'd love to use the plugin, but I'm within an environment where I have to go through proxies between the jenkins hosts.

          Is accessing Jenkin's environment variables not just the same as accessing any environment variable?

          System.out.println("http_proxy=" + env.get("http_proxy"));

          We would like to get this moved forward at work, and I have gotten some availability for now to help drive this forward. Is there any approach that you would need, or anything that I can do to help get this issue resolved?

          Thanks in advance!
          --Proctor

          proctor Steven Proctor added a comment - Is accessing Jenkin's environment variables not just the same as accessing any environment variable? System.out.println("http_proxy=" + env.get("http_proxy")); We would like to get this moved forward at work, and I have gotten some availability for now to help drive this forward. Is there any approach that you would need, or anything that I can do to help get this issue resolved? Thanks in advance! --Proctor

          And looking at the Similar Issues link, there seem to be a few others that are there, one of which is even labeld core and remoting, and is resolved (https://issues.jenkins-ci.org/browse/JENKINS-32326).

          Would any of those help resolve this issue if it has been fixed in core and remoting?

          proctor Steven Proctor added a comment - And looking at the Similar Issues link, there seem to be a few others that are there, one of which is even labeld core and remoting, and is resolved ( https://issues.jenkins-ci.org/browse/JENKINS-32326 ). Would any of those help resolve this issue if it has been fixed in core and remoting?

          People

            Unassigned Unassigned
            rubyisbeautiful Bryan Taylor
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: