Running a local Jenkins plugin repository?

[Andrew Ducker]

Jenkins plugins are downloaded from a wide variety of sources (as the Jenkins downloads site actually forward you on to a mirror).

Our security people aren't willing to open up arbitrary locations to allow Jenkins to pull in updated plugins, and managing them by hand is a massive pain (particularly when there are dependencies).

The easiest thing to do, for us, would be to have an internal Jenkins Plugin repository which could be given persmission to automatically pull the latest versions and made them available inside our firewall - effectively running a private mirror.

Is this something that is currently possible?

Thanks,

Andy

[Daniel Beck]

> On 20.12.2016, at 15:18, Andrew Ducker <and...@ducker.org.uk> wrote:
>
> … security people aren't willing to open up arbitrary locations …
>
> … an internal Jenkins Plugin repository which could be given persmission to automatically pull the latest versions …

This makes no sense at all to me. What am I missing here? There's only a handful of mirrors, and the full list is at http://mirrors.jenkins-ci.org/status.html

You could try running https://github.com/yandex-qatools/juseppe for hosting your own update site. Couple with a script that scrapes http://updates.jenkins-ci.org/latest/ should do it.

[Guy Matz]

This look promising: https://wiki.jenkins-ci.org/display/JENKINS/UpdateSites+Manager+plugin

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/95C54F62-3EB9-45D4-AE57-B57112BE9335%40beckweb.net.

For more options, visit https://groups.google.com/d/optout.