Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-36441

Provide an engine for plugin bundling in the Jenkins2 core

    Details

    • 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

            Activity

            Hide
            danielbeck Daniel Beck added a comment -

            I would think a simpler approach of update if installed is older

            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.

            Show
            danielbeck Daniel Beck added a comment - I would think a simpler approach of update if installed is older 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.
            Hide
            jglick Jesse Glick added a comment -

            The PR claims that the JIRA issue has a description of the ultimate use case, but I guess I am not seeing it here. What does

            it's impossible to safely unbundle Core functionality

            refer to, concretely? What does “unbundle core functionality” mean? Splitting plugins from core? That is handled by the detached list.

            Show
            jglick Jesse Glick added a comment - The PR claims that the JIRA issue has a description of the ultimate use case, but I guess I am not seeing it here. What does it's impossible to safely unbundle Core functionality refer to, concretely? What does “unbundle core functionality” mean? Splitting plugins from core? That is handled by the detached list.
            Hide
            stephenconnolly Stephen Connolly added a comment -

            Yep I do not understand this or the PR

            Show
            stephenconnolly Stephen Connolly added a comment - Yep I do not understand this or the PR
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            I'll follow-up on it after my vacation

            Show
            oleg_nenashev Oleg Nenashev added a comment - I'll follow-up on it after my vacation
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            I didn't. I have no interest in delivering it during my spare time, hence I am just going to close it

            Show
            oleg_nenashev Oleg Nenashev added a comment - I didn't. I have no interest in delivering it during my spare time, hence I am just going to close it

              People

              • Assignee:
                Unassigned
                Reporter:
                oleg_nenashev Oleg Nenashev
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated: