-
Bug
-
Resolution: Fixed
-
Critical
-
None
When installing a new plugin, Jenkins automatically also installs dependencies that are not installed.
Unfortunately, it's possible to disable plugins, whose effect to the Jenkins runtime is effectively the same as if the plugin was missing – except that there's currently no process to enable plugins that are disabled.
Similar to DownloadJobs added for missing dependencies, there should be EnableJobs that enable disabled dependencies (or another approach, but this would nicely mirror the existing DownloadJob one).
We received multiple reports from users affected by this when upgrading to 2.0 and installing the pipeline plugins, so this is critical.
- causes
-
JENKINS-69183 It is impossible to update disabled plugins
- Closed
- is duplicated by
-
JENKINS-34504 Jenkins got unusable after upgrading to 2.0 version
- Resolved
- is related to
-
JENKINS-21486 Refuse to load a plugin if dependencies are disabled or outdated
- Resolved
-
JENKINS-21485 AdministrativeMonitor for plugins that have failed
- Resolved
-
JENKINS-32340 Cannot enable disabled dependencies
- Resolved
-
JENKINS-34434 GitHub Plugins cause dead Jenkins after 2.0 upgrade
- Resolved
- links to