ALL plugins that should be disabled should be managed like this while jenkins is not running - otherwise you have to restart jenkins once it comes up in order to disable them. If you try, for example, to disable blueocean while Jenkins is running, you'll discover there are 26ish plugins that must be disabled in a particular order (and you'll still be left with two that can't be disabled...) but by doing it on the file system you do not need to care about order.
Beware, however, that a disabled plugin will still elicit a "newer version is available" message in pluginManager - and accepting an upgrade WILL re-enable it.
Finally, bundled plugins can't be uninstalled, you can only disable them.
Comments
1 comment
ALL plugins that should be disabled should be managed like this while jenkins is not running - otherwise you have to restart jenkins once it comes up in order to disable them. If you try, for example, to disable blueocean while Jenkins is running, you'll discover there are 26ish plugins that must be disabled in a particular order (and you'll still be left with two that can't be disabled...) but by doing it on the file system you do not need to care about order.
Beware, however, that a disabled plugin will still elicit a "newer version is available" message in pluginManager - and accepting an upgrade WILL re-enable it.
Finally, bundled plugins can't be uninstalled, you can only disable them.
Please sign in to leave a comment.