Details
-
Epic
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
Plugin Management tooling
-
Description
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.
Attachments
Issue Links
- relates to
-
JENKINS-53506 Update all installed plugins to latest version
-
- Closed
-
-
JENKINS-51929 Create "mvn incrementals:update" equivalents for YAML and BOM definitions
-
- Resolved
-
- links to
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
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. |
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 | James Strachan [ jstrachan ] |
| Link |
This issue relates to |
| Link |
This issue relates to |
| Assignee | James Strachan [ jstrachan ] |
| Labels | gsoc-2019-project-idea |
| Description |
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. |
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. |
| Remote Link | This issue links to "GSoC Project Idea (Web Link)" [ 22516 ] |
| Labels | gsoc-2019-project-idea | gsoc-2019 gsoc-2019-project-idea |
Natasha Stopa
made changes -
| Assignee | Natasha Stopa [ stopalopa ] |
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Kristin Whetstone
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child | JENKINS-58129 [ 200174 ] |
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child | JENKINS-58217 [ 200277 ] |
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Description |
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. |
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_ a live Jenkins instance. |
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child | JENKINS-58229 [ 200289 ] |
Natasha Stopa
made changes -
| Epic Child | INFRA-2162 [ 200290 ] |
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Kristin Whetstone
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child | JENKINS-58652 [ 200932 ] |
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child | JENKINS-59066 [ 201446 ] |
Natasha Stopa
made changes -
| Epic Child |
|
Natasha Stopa
made changes -
| Epic Child |
|
Bujji Reddy
made changes -
| Epic Child | JENKINS-61879 [ 205747 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
