Status: Closed (View Workflow)
The typical system administrator, to urgently recover from a problem, will need to use local system commands to disable plugins indicated a problem in the Jenkins logs.
The first step is to include a "README" in the install and/or plugin directories. This readme file may be as simple as to link to the Jenkins online documentation describing the file structure and configurations.
Secondly, there should be clear documentation on the "manual" backup/restore/disabling plugins and their configurations.
Lastly, if it is not currently possible to disable a plugin via the command line and/or config update a process should be added to Jenkins to do so.
See thread https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFuG9t_F4zL%3D7ncg53XdZG9dZD-GdWQ1dtTN53DrKjm8g%40mail.gmail.com
- relates to
JENKINS-33843 It's not possible to disable/uninstall optional dependencies
- links to
|Field||Original Value||New Value|
|Summary||There should be a command line mechism to disable plugins||There should be a command line mechanism to disable plugins|
|Workflow||JNJira [ 161375 ]||JNJira + In-Review [ 180675 ]|
|Assignee||Ramon Leon [ mramonleon ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Remote Link||This issue links to "#3648 in core (Web Link)" [ 21840 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Progress [ 3 ]||Fixed but Unreleased [ 10203 ]|
|Released As||(towards) 2.151|
|Status||Fixed but Unreleased [ 10203 ]||Closed [ 6 ]|
This issue relates to