Open timja opened 5 years ago
Hello,
I also have this problem with the Jenkins Docker image
https://hub.docker.com/r/jenkins/jenkins
and the jenkins-plugin-cli. There it is not possiblity to add the parameter
-Dhttps.proxyHost=myproxy.server.com -Dhttps.proxyPort=8080
and so on to the command line call of jenkins-plugin-cli but you can use the JAVA_TOOL_OPTIONS environment variable like
JAVA_TOOL_OPTIONS="-Dhttps.proxyHost=myproxy.server.com -Dhttps.proxyPort=8080 -Dhttp.nonProxyHosts=localhost|127.*|[::1]"
[The readme of the Jenkins image (without that information) can be found at
https://github.com/jenkinsci/docker/blob/master/README.md|https://hub.docker.com/r/jenkins/jenkins]
[Originally duplicated by: JENKINS-63228]
When trying to install a plugin with the Jenkins CLI and providing a URL as argument, the proxy configuration of the Jenkins master does not seem to be taken into account.
For example if I use the following command:
java -jar jenkins-cli.jar -logger FINE -s https://my.jenkinsexample.com -noCertificateCheck -auth myUser:myPassword install-plugin https://jenkins-updates.cloudbees.com/download/plugins/cloudbees-aws-cli/1.5.9/cloudbees-aws-cli.hpi
But requires to be behind an HTTP proxy to be able to download that plugin, it fails with:
ERROR: Unexpected exception occurred while performing install-plugin command. java.net.ConnectException: Connection timed out
Even if I have a proxy configured under *Manage Jenkins > Manage Plugins > Advanced*.
Evidence
Workaround
Only workaround seem to be to set the proxy via system properties on the master:
Originally reported by allan_burdajewicz, imported from: CLI command install-plugin does not take Proxy configuration into account