|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Note that as of 1.483 Jenkins will at least display non-default update centers.
A GUI to manage them may be trickier. Each needs to have a unique ID (so the proposed UI would not fly); and they typically have their own certificates too.
(As an aside, Jenkins Enterprise by CloudBees includes a plugin which can create custom UCs that can incorporate upstream UCs but add custom additions; and then generates a plugin on the fly which can be installed in another Jenkins instance to connect to this custom UC including certificate.)