-
Bug
-
Resolution: Fixed
-
Major
PluginManager already keeps track of plugins that have failed to start. We should add an AdministrativeMonitor that pops up if this list of failed plugins is non-empty.
This will help administrators discover problems before unsatisfied dependencies starts breaking builds left and right.
- is duplicated by
-
JENKINS-30644 Jenkins should manage better the plugin dependencies when disabling/uninstalling a plugin
-
- Resolved
-
- is related to
-
JENKINS-23150 Warn users about invalid plugin configurations
-
- Resolved
-
-
JENKINS-14616 Corrupted plugin updates leads to plugin uninstall and lost job configuration
-
- Open
-
-
JENKINS-21486 Refuse to load a plugin if dependencies are disabled or outdated
-
- Resolved
-
-
JENKINS-22095 Failed inspecting plugin: archive is not a ZIP archive
-
- Resolved
-
-
JENKINS-34494 Enable disabled (transitive) dependencies when installing a new plugin
-
- Resolved
-
[JENKINS-21485] AdministrativeMonitor for plugins that have failed
Labels | New: robustness |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Link | New: This issue is related to JENKINS-14616 [ JENKINS-14616 ] |
Link |
New:
This issue is related to |
Link |
New:
This issue is duplicated by |
Assignee | New: Félix Belzunce Arcos [ fbelzunc ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Link |
New:
This issue is related to |