• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • jenkins 2.7.1

      bundling plugins in a war as documented overwrites any upgraded plugin with an old plugin on restart .

      As plugin bundling was a way to produce a war for distribution with default plugins the removal of this feature breaks a documented use case.

          [JENKINS-36583] plugin bundling broken

          Oleg Nenashev added a comment -

          Yes, it overrides updated plugins on startup:  https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/PluginManager.java#L926-L...

          teilo If you want to fix it, there is a ready code in https://github.com/jenkinsci/jenkins/pull/2436/ for JENKINS-36441. Actually hit the same issue. We just need to decouple it to a separate PR

          Oleg Nenashev added a comment - Yes, it overrides updated plugins on startup:   https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/PluginManager.java#L926-L ... teilo If you want to fix it, there is a ready code in https://github.com/jenkinsci/jenkins/pull/2436/ for JENKINS-36441 . Actually hit the same issue. We just need to decouple it to a separate PR

          Jesse Glick added a comment -

          Well the documentation has been amended to say that this use case is no longer supported as of Jenkins 2.0. So I think this should just be closed.

          Jesse Glick added a comment - Well the documentation has been amended to say that this use case is no longer supported as of Jenkins 2.0. So I think this should just be closed.

          James Nord added a comment -

          fixed by documentation

          James Nord added a comment - fixed by documentation

            Unassigned Unassigned
            teilo James Nord
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: