-
Bug
-
Resolution: Fixed
-
Major
Implied dependencies are not considered at all on the setup dialog. If we think they're so important that we don't allow disabling the plugins when an implied dependent plugin is enabled, we should consider them important enough to install them when such a plugin is installed, no? Otherwise this could result in a giant mess of broken plugins.
Assigning to Tom as he wrote the plugin wizard. CC kzantow
- is related to
-
JENKINS-33308 Plugin Manager needs to consider implied plugin dependencies
-
- Resolved
-
- links to
[JENKINS-33296] Initial plugin setup needs to consider implied dependencies
Assignee | Original: Tom FENNELLY [ tfennelly ] | New: Keith Zantow [ kzantow ] |
Link |
New:
This issue is related to |
Labels | Original: 2.0 | New: 2.0 2.0-planned |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Description |
Original:
Implied dependencies are not considered at all on the setup dialog. If we think they're so important that we don't allow disabling the plugins when an implied dependent plugin is enabled, we should consider them important enough to install them when such a plugin is installed, no? Otherwise this could result in a giant mess of broken plugins. Assigning to Tom as he wrote the plugin wizard. CC [~kzantow] |
New:
Implied dependencies are not considered at all on the setup dialog. If we think they're so important that we don't allow disabling the plugins when an implied dependent plugin is enabled, we should consider them important enough to install them when such a plugin is installed, no? Otherwise this could result in a giant mess of broken plugins. Assigning to Tom as he wrote the plugin wizard. CC [~kzantow] PR: https://github.com/jenkinsci/jenkins/pull/2122 |
Description |
Original:
Implied dependencies are not considered at all on the setup dialog. If we think they're so important that we don't allow disabling the plugins when an implied dependent plugin is enabled, we should consider them important enough to install them when such a plugin is installed, no? Otherwise this could result in a giant mess of broken plugins. Assigning to Tom as he wrote the plugin wizard. CC [~kzantow] PR: https://github.com/jenkinsci/jenkins/pull/2122 |
New:
Implied dependencies are not considered at all on the setup dialog. If we think they're so important that we don't allow disabling the plugins when an implied dependent plugin is enabled, we should consider them important enough to install them when such a plugin is installed, no? Otherwise this could result in a giant mess of broken plugins. Assigning to Tom as he wrote the plugin wizard. CC [~kzantow] |
Remote Link | New: This issue links to "PR 2122 (Web Link)" [ 14071 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 169195 ] | New: JNJira + In-Review [ 198558 ] |