-
Bug
-
Resolution: Fixed
-
Critical
According to jglick, Jenkins lets a plugin start even if some of its dependencies are missing.
Since missing dependencies might only get much later (for example during builds), it's better to let those plugins fail earlier than later.
Combined with JENKINS-21485, this will make Jenkins boot more reliable and help administrators catch problems more quickly.
- depends on
-
JENKINS-28942 Allow plugins to declare that they do not use certain implied dependencies
- Open
- is blocking
-
JENKINS-36666 Jenkins startup fails due to cyclic dependency miscalculation
- Resolved
- is duplicated by
-
JENKINS-28955 Jenkins unusable after downgrade from latest weekly release to LTS
- Resolved
-
JENKINS-30644 Jenkins should manage better the plugin dependencies when disabling/uninstalling a plugin
- Resolved
-
JENKINS-32558 Disabled plugins should be managed as missed dependencies on Jenkins startup
- Resolved
-
JENKINS-30432 "Scripts not permitted to use method" in Jenkins Workflow
- Resolved
-
JENKINS-33357 Gradle class not found Servlet Exception prevents Configure Pages from loading
- Closed
- is related to
-
JENKINS-20155 Select All in /pluginManager/ should not select plugins with a compatWarning
- Resolved
-
JENKINS-21485 AdministrativeMonitor for plugins that have failed
- Resolved
-
JENKINS-34073 Plugin dependency fix (JENKINS-21486) not visible enough
- Resolved
-
JENKINS-34494 Enable disabled (transitive) dependencies when installing a new plugin
- Resolved
-
JENKINS-24046 Updating a WAR should unpin a plugin which is now older than the bundled plugin
- Resolved
-
JENKINS-23150 Warn users about invalid plugin configurations
- Resolved
- relates to
-
JENKINS-52665 Treat plugin dependency mismatches involving snapshots as nonfatal
- Resolved
- links to