-
Bug
-
Resolution: Unresolved
-
Major
-
None
If a plugin A has an optional dependency on plugin B, and has marked an @Extension (optional=true), Jenkins will properly fail to load that extension. However, if plugin B is then later installed, the optional dependencies from plugin A are not re-evaluated.
Jenkins should keep track of optional extensions which failed to load, and retry them when new plugins are installed. Perhaps it could only due so if the plugin for that extension expressed an optional dependency on the newly installed plugin, but even that doesn't seem necessary?
This is really just a usability issue (since you can restart to fix it), but may prove frustrating for novice users.
- is related to
-
JENKINS-49026 Plugins are not installed in right order in case of optional dependency
-
- Open
-
- relates to
-
JENKINS-50336 Optional extensions are not picked up after installing the optional dependency
-
- Resolved
-
-
JENKINS-19508 Replace @Extension(optional=true) and optional dependencies with bridge plugins
-
- Open
-
- links to
[JENKINS-14392] Optional Extensions should be reloaded when dependencies are dynamically loaded
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 145028 ] | New: JNJira + In-Review [ 191314 ] |
Resolution | Original: Duplicate [ 3 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Link |
Original:
This issue duplicates |
Status | Original: Reopened [ 4 ] | New: Open [ 1 ] |
Summary | Original: Optional Extensions are reloaded when dependencies are dynamically loaded | New: Optional Extensions should be reloaded when dependencies are dynamically loaded |
Remote Link | New: This issue links to "CloudBees Internal CJP-6696 (Web Link)" [ 19058 ] |
Link | New: This issue is related to JENKINS-49026 [ JENKINS-49026 ] |
Link |
New:
This issue relates to |
Link | New: This issue relates to JENKINS-19508 [ JENKINS-19508 ] |