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

HTTP Client to upload CRX packages does not adhere to no-proxy patterns

XMLWordPrintable

      Our Jenkins has a proxy configured with exceptions. But the plugin does not obey to these exceptions. So the deployment fails because the HTTP proxy cannot connect to the host. Testing the connection fails with:

      FATAL: Failed to deploy package: Failed to login to <redacted>
java.io.IOException: Failed to login to <redacted>
at org.jenkinsci.plugins.graniteclient.GraniteClientExecutor.execute(GraniteClientExecutor.java:90)
at org.jenkinsci.plugins.graniteclient.DeployPackageCallable.invoke(DeployPackageCallable.java:129)
at org.jenkinsci.plugins.graniteclient.DeployPackageCallable.invoke(DeployPackageCallable.java:46)
at hudson.FilePath.act(FilePath.java:996)

      When a HttpAsyncClient is created through GraniteClientGlobalConfig#getInstance(), the proxy configuration is created right away without checking for the exceptions defined by hudson.ProxyConfiguration#getNoProxyPatterns().

            Unassigned Unassigned
            cgi_robertgacki Robert Gacki
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: