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

Jenkins does not install right plugin version, also plugin compbility issue

      Hi,

      I had jenkins (version 2.263.4) installed on my server, suddenly while redeploying, the plugins installation started failing with the below error

      022-04-15 02:37:25.111+0000 [id=42] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Token Macro Plugin v270.v8c2ce50dc4fc (token-macro)
      java.io.IOException: Failed to load: Token Macro Plugin (270.v8c2ce50dc4fc)

      • Jenkins (2.277.1) or higher required
        at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:952)
        at hudson.PluginManager$2$1$1.run(PluginManager.java:549)
        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:1131)
        at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)
        at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
        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)
        2022-04-15 02:37:25.112+0000 [id=42] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Folders Plugin v6.714.v79e858ef76a_2 (cloudbees-folder)
        java.io.IOException: Failed to load: Folders Plugin (6.714.v79e858ef76a_2)
      • Jenkins (2.277.1) or higher required

      Also while installing any plugin along with version number, it is not installing the right version number.

      Example:
       java -jar /jenkins-cli.jar -s http://localhost:8080 -auth admin:<fake> install-plugin cloudbees-folder:6.688.vfc7a_a_69059e0 -restart
      has below manifest:

      Manifest-Version: 1.0
      Hudson-Version: 2.277.1
      Plugin-Dependencies: credentials:2.6.1;resolution:=optional
      Implementation-Title: cloudbees-folder
      Long-Name: Folders Plugin
      Implementation-Version: 6.714.v79e858ef76a_2
      Group-Id: org.jenkins-ci.plugins
      Minimum-Java-Version: 1.8
      Plugin-License-Name: MIT
      Specification-Title: This plugin allows users to create "folders" to o
      rganize jobs. Users can define custom taxonomies (like by project t
      ype, organization type etc). Folders are nestable and you can define
      views within folders. Maintained by CloudBees, Inc.
      Plugin-ScmUrl: https://github.com/jenkinsci/cloudbees-folder-plugin
      Plugin-Version: 6.714.v79e858ef76a_2 ----------------------> different than stated while installation
      Jenkins-Version: 2.277.1
      Url: https://github.com/jenkinsci/cloudbees-folder-plugin/
      Short-Name: cloudbees-folder
      Plugin-License-Url: https://opensource.org/licenses/MIT
      Compatible-Since-Version: 5.2
      Plugin-Developers:
      Extension-Name: cloudbees-folder
      Build-Jdk-Spec: 1.8
      Created-By: Maven Archiver 3.5.2

          [JENKINS-68306] Jenkins does not install right plugin version, also plugin compbility issue

          Markus Winter added a comment -

          There is no longer an update site for your Jenkins version 2.263.4

          So whenever you install a plugin it will find potentially something that is newer.

          Note that you can't specify a dedicated version of a plugin via the CLI. According to the documentation the version you specify is a minimum version

          If the short name includes a minimum version number (like
           ?findbugs:1.4?), and there are multiple update centers publishing
           different versions, the update centers will be searched in order
           for the first one publishing a version that is at least the
           specified version.

          So you should upgrade your Jenkins to a newer version. 2.263.4 is now over 1 year old and has some security issues.

          Markus Winter added a comment - There is no longer an update site for your Jenkins version 2.263.4 So whenever you install a plugin it will find potentially something that is newer. Note that you can't specify a dedicated version of a plugin via the CLI. According to the documentation the version you specify is a minimum version If the short name includes a minimum version number (like ?findbugs:1.4?), and there are multiple update centers publishing different versions, the update centers will be searched in order for the first one publishing a version that is at least the specified version. So you should upgrade your Jenkins to a newer version. 2.263.4 is now over 1 year old and has some security issues.

          Hi mawinter69,
          Thank you answering. How can we check if the update site is available for given jenkins version?

          Sayali Gaikawad added a comment - Hi mawinter69 , Thank you answering. How can we check if the update site is available for given jenkins version?

          Markus Winter added a comment -

          Markus Winter added a comment - Visit https://updates.jenkins.io/update-center.json?version=2.263.4  and you will see that you get redirected to https://updates.jenkins.io/dynamic-stable-2.277.1/update-center.json  

          Basil Crow added a comment -

          In general, the Update Center supports Jenkins core releases for 400 days after the Jenkins core release was shipped.

          Basil Crow added a comment - In general, the Update Center supports Jenkins core releases for 400 days after the Jenkins core release was shipped.

            stopalopa Natasha Stopa
            sayaligaikawad Sayali Gaikawad
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: