-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
jenkins-2.x
I am working on the custom bundle of Jenkins based on the 2.0 baseline. In this custom bundle I would like to extend the functionality of the default UpdateCenter.
My use-cases:
- Ability to extend REST API (new commands for very custom cases)
- Ability to manage update sites from the code according to the installation settings
- Ability to alter UpdateCenter UIs and maybe tweak the installation Wizard
According to the current Jenkins design, it cannot be done via a classic extension point in a plugin, but it can be done in a library. Since UpdateCenter can unlikely provide extension points for our cases, it seems the best way would be to override the UpdateCenter instance.
I propose to add a system property, which would allow to instantiate Jenkins with a custom UpdateCenter.
[JENKINS-34733] Make the UpdateCenter overridable for custom Jenkins WAR packages
Description |
Original:
My team is working on the custom bundle of Jenkins based on the 2.0 baseline. In this custom bundle we would like to extend the functionality of the default UpdateCenter. Our use-cases: * Ability to extend REST API (new commands for very custom cases) * Ability to manage update sites from the code according to the installation settings * Ability to alter UpdateCenter UIs and maybe tweak the installation Wizard According to the current Jenkins design, it cannot be done via a classic extension point in a plugin, but it can be done in a library. Since UpdateCenter can unlikely provide extension points for our cases, it seems the best way would be to override the UpdateCenter instance. I propose to add a system property, which would allow to instantiate Jenkins with a custom UpdateCenter. |
New:
I am working on the custom bundle of Jenkins based on the 2.0 baseline. In this custom bundle I would like to extend the functionality of the default UpdateCenter. My use-cases: * Ability to extend REST API (new commands for very custom cases) * Ability to manage update sites from the code according to the installation settings * Ability to alter UpdateCenter UIs and maybe tweak the installation Wizard According to the current Jenkins design, it cannot be done via a classic extension point in a plugin, but it can be done in a library. Since UpdateCenter can unlikely provide extension points for our cases, it seems the best way would be to override the UpdateCenter instance. I propose to add a system property, which would allow to instantiate Jenkins with a custom UpdateCenter. |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JNJira [ 170914 ] | New: JNJira + In-Review [ 210019 ] |
Code changed in jenkins
User: Oleg Nenashev
Path:
core/src/main/java/hudson/model/UpdateCenter.java
core/src/main/java/jenkins/model/Jenkins.java
test/src/test/java/hudson/model/UpdateCenterCustomTest.java
http://jenkins-ci.org/commit/jenkins/768da3e241417da47f306ac2e32fbc14c31be8c8
Log:
JENKINS-34733- Allow overriding Jenkins UpdateCenter by a custom implementation (#2332)JENKINS-34733- Allow overriding Jenkins UpdateCenter by a custom implementationJENKINS-34733- Reduce the logging level for the custom update center selection