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

Offer plugin management tooling

XMLWordPrintable

    • Plugin Management tooling

      Jenkins does offer a web UI to manage plugin installation from a live master instance, but in many deployments administrator would like to control installed plugins by version and by tooling, before jenkins master starts.

      • docker official image provides an install-plugins.sh script which evolved far beyond its initial "help script" scope.
      • configuration-as-code implemented plugin installation hack based on PluginSite.Plugin#deploy. (Removed as of v1.8 of JCasC plugin)
      • open-source update center does expose plugins-version.json on casc request so one can manage versions for all hosted plugins, not just latest
      • custom war packager does support plugin installation on his own
      • jenkins evergreen does manage plugin installation based on updates from metadata server, using his own logic implemented by nodejs evergreen client.
      • jenkinsfile-runner does manage plugin installation implemented in Go
      • coreOS provides a groovy script to handle required plugins
      • cloudbees DEV@Cloud uses a set of Chef Ruby recipes for the same purpose
      • etc

       

      Everybody is re-inventing the wheel, partially implementing the "details" of plugin management (signed metadata, artifacts checksums, plugins detached from core, ...). It becomes obvious Jenkins should provide adequate tooling for plugin installation outside a live Jenkins instance. 

          [JENKINS-53767] Offer plugin management tooling

          Nicolas De Loof created issue -
          Baptiste Mathus made changes -
          Description Original: Jenkins do offer a web UI to manage plugin installation from a live master instance, but in many deployment administrator would like to control installed plugins by version and by tooling, before jenkins master starts.
           * docker official image provides an install-plugins.sh script which evolved far beyond it's initial "help script" scope.
           * configuration-as-code implemented plugin installation hack based on PluginSite.Plugin#deploy.
           * open-source update center do expose plugins-version.json on casc request so one can manage versions for all hosted plugins, not just latest
           * custom war packager do support plugin installation on his own
           * jenkins evergreen do manage plugin installation based on updates from metadata server, using his own logic implemented by nodejs evergreen client.
           * jenkinsfile-runner do manage plugin installation implemented in Go
           * coreOS provides a [groovy script|https://github.com/coreos/jenkins-os/blob/master/init.groovy] to handle required plugins
           * cloudbees DEV@Cloud uses a set of Chef Ruby recipes for the same purpose
           * etc

           

          Everybody is re-inventing the wheel, partially implementing the "details" of plugin management (signed metadata, artifacts checksums, plugins detached from core, ...). It becomes obvious Jenkins should provide adequate tooling for plugin installation _outside_ jenkins live instance.            		New: Jenkins does offer a web UI to manage plugin installation from a live master instance, but in many deployments administrator would like to control installed plugins by version and by tooling, before jenkins master starts.
           * docker official image provides an install-plugins.sh script which evolved far beyond its initial "help script" scope.
           * configuration-as-code implemented plugin installation hack based on PluginSite.Plugin#deploy.
           * open-source update center does expose plugins-version.json on casc request so one can manage versions for all hosted plugins, not just latest
           * custom war packager does support plugin installation on his own
           * jenkins evergreen does manage plugin installation based on updates from metadata server, using his own logic implemented by nodejs evergreen client.
           * jenkinsfile-runner does manage plugin installation implemented in Go
           * coreOS provides a [groovy script|https://github.com/coreos/jenkins-os/blob/master/init.groovy] to handle required plugins
           * cloudbees DEV@Cloud uses a set of Chef Ruby recipes for the same purpose
           * etc

           

          Everybody is re-inventing the wheel, partially implementing the "details" of plugin management (signed metadata, artifacts checksums, plugins detached from core, ...). It becomes obvious Jenkins should provide adequate tooling for plugin installation _outside_ jenkins live instance. 
          James Strachan made changes -
          Assignee New: James Strachan [ jstrachan ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-51929 [ JENKINS-51929 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-53506 [ JENKINS-53506 ]
          Oleg Nenashev made changes -
          Assignee Original: James Strachan [ jstrachan ]
          Oleg Nenashev made changes -
          Labels New: gsoc-2019-project-idea
          Joseph Petersen (old) made changes -
          Description Original: Jenkins does offer a web UI to manage plugin installation from a live master instance, but in many deployments administrator would like to control installed plugins by version and by tooling, before jenkins master starts.
           * docker official image provides an install-plugins.sh script which evolved far beyond its initial "help script" scope.
           * configuration-as-code implemented plugin installation hack based on PluginSite.Plugin#deploy.
           * open-source update center does expose plugins-version.json on casc request so one can manage versions for all hosted plugins, not just latest
           * custom war packager does support plugin installation on his own
           * jenkins evergreen does manage plugin installation based on updates from metadata server, using his own logic implemented by nodejs evergreen client.
           * jenkinsfile-runner does manage plugin installation implemented in Go
           * coreOS provides a [groovy script|https://github.com/coreos/jenkins-os/blob/master/init.groovy] to handle required plugins
           * cloudbees DEV@Cloud uses a set of Chef Ruby recipes for the same purpose
           * etc

           

          Everybody is re-inventing the wheel, partially implementing the "details" of plugin management (signed metadata, artifacts checksums, plugins detached from core, ...). It becomes obvious Jenkins should provide adequate tooling for plugin installation _outside_ jenkins live instance.            		New: Jenkins does offer a web UI to manage plugin installation from a live master instance, but in many deployments administrator would like to control installed plugins by version and by tooling, before jenkins master starts.
           * docker official image provides an install-plugins.sh script which evolved far beyond its initial "help script" scope.
           * configuration-as-code implemented plugin installation hack based on PluginSite.Plugin#deploy. (Removed as of v1.8 of JCasC plugin)
           * open-source update center does expose plugins-version.json on casc request so one can manage versions for all hosted plugins, not just latest
           * custom war packager does support plugin installation on his own
           * jenkins evergreen does manage plugin installation based on updates from metadata server, using his own logic implemented by nodejs evergreen client.
           * jenkinsfile-runner does manage plugin installation implemented in Go
           * coreOS provides a [groovy script|https://github.com/coreos/jenkins-os/blob/master/init.groovy] to handle required plugins
           * cloudbees DEV@Cloud uses a set of Chef Ruby recipes for the same purpose
           * etc

           

          Everybody is re-inventing the wheel, partially implementing the "details" of plugin management (signed metadata, artifacts checksums, plugins detached from core, ...). It becomes obvious Jenkins should provide adequate tooling for plugin installation _outside_ jenkins live instance. 
          Oleg Nenashev made changes -
          Remote Link New: This issue links to "GSoC Project Idea (Web Link)" [ 22516 ]
          Oleg Nenashev made changes -
          Labels Original: gsoc-2019-project-idea New: gsoc-2019 gsoc-2019-project-idea
          Natasha Stopa made changes -
          Assignee New: Natasha Stopa [ stopalopa ]

            stopalopa Natasha Stopa
            ndeloof Nicolas De Loof
            Votes:
            11 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated:
              Resolved: