Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-34733

Make the UpdateCenter overridable for custom Jenkins WAR packages

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Environment:
      jenkins-2.x
    • Similar Issues:

      Description

      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.

        Attachments

          Activity

          oleg_nenashev Oleg Nenashev created issue -
          oleg_nenashev Oleg Nenashev made changes -
          Field Original Value New Value
          Description 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.
          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.
          oleg_nenashev Oleg Nenashev made changes -
          Assignee Oleg Nenashev [ oleg_nenashev ]
          oleg_nenashev Oleg Nenashev made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          oleg_nenashev Oleg Nenashev made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 170914 ] JNJira + In-Review [ 210019 ]

            People

            Assignee:
            oleg_nenashev Oleg Nenashev
            Reporter:
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: