Open bbcmicrocomputer opened 7 years ago
Reported in the jenkins-charm repo at https://github.com/jenkinsci/jenkins-charm/issues/31.
We could detect Juju's proxy bits in cwr and warn the user that any CI system will need to be configured if that system does not honor the ubuntu
user's proxy info (currently stored in /home/ubuntu/.juju-proxy
).
I'll leave this open for now pending a decision on how best to notify cwr
users on potentially missing proxy config.
cwr needs to add proxy support if it wants to support flexible lab deployments.
I needed to add:
http_proxy https_proxy no_proxy
variables/proxy config to the following menu items in Jenkins to install required plugins and run tests:
http://jenkins:8080/configure (Environment variables) http://jenkins:8080/pluginManager/advanced
Ideally the charm should just read the 'http_*', 'no_proxy' environment variables setup by Juju and adjust Jenkins automatically without user intervention.
This could be punted as a Jenkins charm issue but I'm filing it here to track.