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

Rundeck does not use Jenkins proxy settings

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Component/s: rundeck-plugin
    • Environment:
    • Similar Issues:

      Description

      Hello,

      I have a problem to connect my Jenkins Rundeck plugin to Rundeck application.
      I think Jenkins Rundeck plugin does not use Jenkins proxy setting configured in "Manage Jenkins > Manage Plugins > Advanced".

      In fact, when I configure Jenkins Rundeck plugin in "Manage Jenkins > Configure System", I have this error message when I click on "Test Connection" :
      We couldn't find a live Rundeck instance at "http://my_url/rundeck".

      But, when I test url "http://my_url/rundeck" during the HTTP Proxy Configuration in "Manage Jenkins > Manage Plugins > Advanced", I have a "Success".

      If I configure the proxy settings in the file Jenkins\jenkins.xml like this (see below), my Rundeck instance is detected and I can link Rundeck job to my Jenkins jobs.

      <arguments>-Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -Dhttp.proxyHost=MY_PROXY -Dhttp.proxyPort=MY_PROXY_PORT -jar "%BASE%\jenkins.war" --httpPort=8080</arguments>

      But this solution cause another problems, because I think when we configure proxy in the jenkins.xml file, the proxy settings configured on the Jenkins UI is by passed and then SVN does not works...

      Please, can you help me?
      Maybe we can configure manually proxy only for Jenkins Rundeck plugin in a file configuration? Another idea?
      Feel free to ask me if you need more informations.

      Thanks in advance.
      Regards

        Attachments

          Activity

          Hide
          ahammar Anders Hammar added a comment -

          I've run into the same problem and the root cause is in the underlaying rundeck API java client library. What I did locally was to patch that library and did a custom build of the plugin.

          The proxy stuff is changing in the upcoming version for v13 of the Rundeck API. It will then pick up the http.proxyHost et al system properties. If we want the plugin to use the Jenkins proxy config hte plugin needs to be updated to handle that.

          Show
          ahammar Anders Hammar added a comment - I've run into the same problem and the root cause is in the underlaying rundeck API java client library. What I did locally was to patch that library and did a custom build of the plugin. The proxy stuff is changing in the upcoming version for v13 of the Rundeck API. It will then pick up the http.proxyHost et al system properties. If we want the plugin to use the Jenkins proxy config hte plugin needs to be updated to handle that.

            People

            • Assignee:
              vbehar Vincent Behar
              Reporter:
              kevin_dfv Kevin Defives
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: