Our current configuration is very simple. We use the backend-update-center2 
<https://github.com/jenkinsci/backend-update-center2> to generate the 
Update Sites .json of our own plugins and that's it. Every Jenkins instance 
is then configured with both public and private Update Sites. The only 
detail is that we use the same artifact repository for hosting our own 
plugins and as a *proxy* for the public repository. Still, separate 
repositories.

Next we would like to improve the overall experience with the available 
plugins by first pointing out their current reliability (for example with 
ratings) and improve the communication around each plugin across the 
company. For instance, my team is using a plugin X and, from the plugin 
information, I find out that another team far far away is also using it for 
a similar use case. It might not make sense in the public context, but 
everything that triggers this sort of communication is very welcome for 
exchange of experiences.

I was wondering that maybe the *backend-update-center2* itself could be the 
focus of many improvements in this direction. I've been thinking if a *General 
Plugin Manager* would make sense as a more dynamic layer between the 
artifact repository and the Jenkins instances. We would like, for example, 
to add tags/labels to plugins, create profiles so that every internal team 
has a different set of plugins available, also have a per team management 
of which repositories to use. This General Plugin Manager would be a 
standalone server and very likely, in my opinion, the best place to keep 
dynamic information like those ratings...

Just ideas. I would like to hear some opinions...

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ca3fc6da-4e5a-4750-9dc2-6843bae2755e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to