[Jenkins-infra] Guidance for working around update center access restrictions ...

Jeff predatorvi at gmail.com
Wed Mar 1 18:01:10 UTC 2017

Our Jenkins server is inside a secure environment with very limited
external connectivity.  I was able to finally convince the powers that be
to create an exception in our proxy to allow the Jenkins master to contact
the update center URL.  However when I try to download, it redirects to a
mirror which is currently not allowed.

I'm trying to get exceptions for the mirrors, but if I can limit the
exception requests I need, that would help my cause.

Is it possible to force the update center to go directly to a
jenkins-hosted server (jenkins-ci.org or jenkins.io) instead of a mirror?

What about forcing requests to always use a specific mirror that I can
whitelist so I don't have to allow all possible mirror URLs?

Alternatively is there an easy way to create my own update center with
plugins?   I tried rsync'ing the update center but none of the actual
plugins sync.  I did read through
https://github.com/jenkinsci/backend-update-center2 as an option, but it's
going to take some time to digest it and see if it will work.  If this is
the way to go, I can dedicate more cycles to it.

Regardless, it sure would be nice to be able to solve this more easily in
restricted environments and I'm hoping I'm just missing something obvious.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20170301/f80fe972/attachment.html>

More information about the Jenkins-infra mailing list