Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
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.
Attachments
Issue Links
- is related to
-
-
- Open
-
- relates to
-
-
- Resolved
-
-
JENKINS-19508 Replace @Extension(optional=true) and optional dependencies with bridge plugins
-
- Open
-
- links to
Activity
danielbeck no... I was sure there was a newer issue (about 1 year old) with exactly this, but failed optioanl extension points have never been attempted to be reloaded.
Not just a UX issue as this can have bad consequences.
For example when a plugin is performing some form of "veto" about an action (if some properety is set on a job from the optioanl plugin) can lead to the veto which is implemented in the @extension(optional=true) not being called as it is not active, causing the action which should now be blocked from being able to happen which can have some bad consequences in the Jenkins instance.
this can now be resolved as a duplicate of 
Was this resolved in
JENKINS-19976?