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

SOASTA CloudTest Plugin ignores "No Proxy Host" configuration

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: cloudtest-plugin
    • Labels:
      None
    • Environment:
      jenkins 1.613
      cloudtest-plugin 2.20
    • Similar Issues:

      Description

      The SOASTA CloudTest plugin seems to ignore Jenkins' "No Proxy Host" configuration.

      We've confirmed that disabling proxy (by removing the details from [JENKINS_URL]/pluginManager/advanced) allows the plugin to work as normal, but enabling the proxy with relevant hosts whitelisted in the "No Proxy Hosts" field, results in connection errors.

      This has also been mentioned on the SOASTA support forums - the "workaround" for a few people has been to disable the proxy, but this is unacceptable for us:
      http://cloudlink.soasta.com/t5/CloudTest-Discussions/Jenkins-Testing-CloudTest-server-doesn-t-look-like-a-CloudTest/td-p/37671

        Attachments

          Activity

          Show
          uzii Uz Imtiazi added a comment - A few of links to the same issue having affected other plugins: https://github.com/jenkinsci/stashnotifier-plugin/issues/41 https://issues.jenkins-ci.org/browse/JENKINS-20251 https://github.com/janinko/ghprb/issues/377
          Hide
          ltyler Lance Tyler added a comment -

          This issue has been fixed in the 2.22 version of the CloudTest plugin

          Show
          ltyler Lance Tyler added a comment - This issue has been fixed in the 2.22 version of the CloudTest plugin
          Hide
          moessi Martin Mössner added a comment - - edited

          We've tried out with version 2.25 of the plugin and found same behaviour as described in this issue (no proxy for will be ignored).

          Back to version 2.22 everything (no proxy for ...) works fine.

          environment: jenkins 2.39

          Thank you
          Martin

          Show
          moessi Martin Mössner added a comment - - edited We've tried out with version 2.25 of the plugin and found same behaviour as described in this issue (no proxy for will be ignored). Back to version 2.22 everything (no proxy for ...) works fine. environment: jenkins 2.39 Thank you Martin

            People

            • Assignee:
              ltyler Lance Tyler
              Reporter:
              uzii Uz Imtiazi
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: