Details
-
Type:
New Feature
-
Status: Open (View Workflow)
-
Priority:
Critical
-
Resolution: Unresolved
-
Component/s: core
-
Labels:
-
Similar Issues:
Description
In Jenkins 2 the legacy plugin bundling engine has been removed. It complicates the code, because no we cannot bundle Jenkins plugins anymore and then support their updates. It means that now it's impossible to safely unbundle Core functionality anymore.
My proposal is to implement a new engine which...
- Would allow bundling of Jenkins plugins into Jenkins WAR file
- Install the plugin if it's not installed during the startup (if it's not disabled)
- Allow updating the version above the bundled one
For such cases I propose to partially restore the bundling engine, but without pinning feature.
Attachments
Issue Links
- is related to
-
JENKINS-36583 plugin bundling broken
-
- Resolved
-
- relates to
-
JENKINS-51306 ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
-
- Resolved
-
- links to
There is (was?) an admin monitor for that. I have concerns about unexpected plugin updates.
The rationale for the two system properties and the 'force plugin version' behavior in the PR also seems to be completely missing from this issue.