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

Version for a given plugin should be taken from environments first when overridden

XMLWordPrintable

    • Evergreen - Milestone 1

      Issue

      In UL 33, it seems like the version for docker-commons that has been installed is the 1.5.

      This version is the one defined in the main section under spec.plugins.
      But this version is overridden to 1.9 under the flavor-specific environments sectionto 1.9.

      The .json available at https://evergreen.jenkins.io/ for 32a278882aee26f7075e2c219a76dcbacc7b7532 (I think this is the one for UL33) seems correct. So I think the bug might be coming from the service side selection for a given plugin.

      This caused the update of my test instance, and it failed to restart, with the following in the logs:

      [SEVERE][2018-08-29 10:08:59] Failed Loading plugin Docker plugin v1.1.5 (docker-plugin) (from jenkins.InitReactorRunner$1 onTaskFailed)
      java.io.IOException: Docker plugin v1.1.5 failed to load.
       - Docker Commons Plugin v1.5 is older than required. To fix, install v1.9 or later.
       - Token Macro Plugin v2.0 is older than required. To fix, install v2.3 or later.
              at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:652)
              at hudson.PluginManager$2$1$1.run(PluginManager.java:517)
              at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
              at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)
              at jenkins.model.Jenkins$5.runTask(Jenkins.java:1066)
              at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)
              at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
              at java.lang.Thread.run(Thread.java:748)
      

      And here's the state on the browser side:

      Expected behavior

      When a plugin is overridden under the environment specific flavor part, the overridden version defined under the flavor should always be the selected one.

            rtyler R. Tyler Croy
            batmat Baptiste Mathus
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: