On Tue, Aug 14, 2012 at 6:51 AM, Christopher Orr <ch...@orr.me.uk> wrote: > Hi there, > > > On 08/13/2012 12:04 PM, Marc Esher wrote: >> >> My Jenkins server is sitting behind a firewall that does not permit >> outbound access to most of the internet. I was able to get an exclusion >> for jenkins-ci.com for purposes of using Jenkins auto updater and >> installing plugins. However, the connection check uses google.com to >> determine whether it's net-connected. Consequently I cannot update >> Jenkins or install plugins because it fails at the connection check step. >> >> Is this configurable? If I could change the connection check to >> jenkins-ci.org, then updates and plugin installs could proceed as >> expected. > > > The connectionCheckUrl is built into the update-center.json file, so it's > not something configurable on your side. > > Even if you did change it, you'd need a firewall exception for > updates.jenkins-ci.org, which redirects to mirrors.jenkins-ci.org, which > then redirects to some hostname in the Jenkins mirror network -- so your > current single firewall exception wouldn't be enough. > > The mirror hostnames are listed here, but there is no definite guarantee > that these will remain stable for any period of time: > http://mirrors.jenkins-ci.org/status.html > > I'm not sure how others in this situation handle it, but a possible > alternative would be to set up an HTTP caching proxy somewhere on your > network that is allowed full internet access, then add that proxy to the > Update Center config. >
Thanks for the info, Chris. Much appreciated. > Regards, > Chris
