I nkew it all the time. This useless signing is just a business case to
sell some extra plugin.
JUst remove that signing code and allow opensoucing everything. Just use a
plain old maven repo and get plugins via dependecy resolution.
Noone wants cloudbees vendor lock in to plugins update site
Nope. You can sign your own update center too.
The code for signing the UC is open source.
The issue is that for the signing to have meaning you need to have the cert
trusted.
There are a number of ways to get the cert trusted. You can drop the cert
into a special directory in $JENKINS_HOME (I
Hi Guys, I meet the same issue.
Then how can I generate an update-center.json JSON file that can be
interpreded by Jenkins.
We do have several plugins which will be used only inner our group, we do
not like to deliver them to jenkins group.
As a solution, I think we should put the plugins
[shameless plug]
http://docs.apps.cloudbees.com/docs/user-guide-bundle/ch14.html
note that link will be changing to
http://docs.apps.cloudbees.com/docs/user-guide-bundle/uc.html
CloudBees have an UpdateCenter plugin that allows Jenkins to serve it's own
UpdateCenter and allows easy configuring
