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

Blue Ocean Docker container fails to load Pipeline plugins

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Running docker run --rm -ti -p 8080:8080 jenkinsci/blueocean:latest results in some plugins failing to load:

      Looks like the latest tag is pointing to the 1.3.3-aa3a547dc4cb tag

      INFO: Listed all plugins
      Dec 14, 2017 10:13:18 PM jenkins.InitReactorRunner$1 onTaskFailed
      SEVERE: Failed Loading plugin Autofavorite for Blue Ocean v1.1.0 (blueocean-autofavorite)
      java.io.IOException: Autofavorite for Blue Ocean v1.1.0 failed to load.
       - Pipeline: Job v2.11.1 is older than required. To fix, install v2.14.1 or later.
      	at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626)
      	at hudson.PluginManager$2$1$1.run(PluginManager.java:516)
      	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
      	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
      	at jenkins.model.Jenkins$7.runTask(Jenkins.java:1090)
      	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
      	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      	at java.lang.Thread.run(Thread.java:745)
      
      Dec 14, 2017 10:13:18 PM jenkins.InitReactorRunner$1 onTaskFailed
      SEVERE: Failed Loading plugin Blue Ocean v1.3.3 (blueocean)
      java.io.IOException: Blue Ocean v1.3.3 failed to load.
       - Autofavorite for Blue Ocean v1.1.0 failed to load. Fix this plugin first.
      	at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626)
      	at hudson.PluginManager$2$1$1.run(PluginManager.java:516)
      	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
      	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
      	at jenkins.model.Jenkins$7.runTask(Jenkins.java:1090)
      	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
      	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      	at java.lang.Thread.run(Thread.java:745)
      
      Dec 14, 2017 10:13:26 PM jenkins.InitReactorRunner$1 onAttained
      INFO: Prepared all plugins
      Dec 14, 2017 10:13:26 PM jenkins.InitReactorRunner$1 onAttained
      INFO: Started all plugins
      Dec 14, 2017 10:13:29 PM jenkins.InitReactorRunner$1 onAttained
      INFO: Augmented all extensions
      Dec 14, 2017 10:13:29 PM jenkins.InitReactorRunner$1 onAttained
      INFO: Loaded all jobs
      
      

        Attachments

          Activity

          Hide
          rtyler R. Tyler Croy added a comment -

          Looks like the latest tag hasn't been updated because of the Docker signing stuff which was recently introducd

          From trusted.ci

          1.3.4: digest: sha256:a1bc17ed858872fd9961130608ae7b9ae40851a704a5af3112a7572070fab88e size: 3666
          Signing and pushing trust metadata
          You are about to create a new root signing key passphrase. This passphrase
          will be used to protect the most sensitive key in your signing system. Please
          choose a long, complex passphrase and be careful to keep the password and the
          key file itself secure and backed up. It is highly recommended that you use a
          password manager to generate the passphrase and keep it safe. There will be no
          way to recover this key. You can find the key in your config directory.
          Enter passphrase for new root key with ID 66e9aff: 
          Enter passphrase for new root key with ID 66e9aff: 
          Enter passphrase for new root key with ID 66e9aff: 
          Enter passphrase for new root key with ID 66e9aff: 
          Enter passphrase for new root key with ID 66e9aff: 
          Enter passphrase for new root key with ID 66e9aff: 
          Enter passphrase for new root key with ID 66e9aff: 
          Enter passphrase for new root key with ID 66e9aff: 
          Enter passphrase for new root key with ID 66e9aff: 
          Enter passphrase for new root key with ID 66e9aff: 
          Enter passphrase for new root key with ID 66e9aff: 
          Enter passphrase for new root key with ID 66e9aff: 
          maximum number of passphrase attempts exceeded
          [Pipeline] }
          
          
          Show
          rtyler R. Tyler Croy added a comment - Looks like the latest tag hasn't been updated because of the Docker signing stuff which was recently introducd From trusted.ci 1.3.4: digest: sha256:a1bc17ed858872fd9961130608ae7b9ae40851a704a5af3112a7572070fab88e size: 3666 Signing and pushing trust metadata You are about to create a new root signing key passphrase. This passphrase will be used to protect the most sensitive key in your signing system. Please choose a long , complex passphrase and be careful to keep the password and the key file itself secure and backed up. It is highly recommended that you use a password manager to generate the passphrase and keep it safe. There will be no way to recover this key. You can find the key in your config directory. Enter passphrase for new root key with ID 66e9aff: Enter passphrase for new root key with ID 66e9aff: Enter passphrase for new root key with ID 66e9aff: Enter passphrase for new root key with ID 66e9aff: Enter passphrase for new root key with ID 66e9aff: Enter passphrase for new root key with ID 66e9aff: Enter passphrase for new root key with ID 66e9aff: Enter passphrase for new root key with ID 66e9aff: Enter passphrase for new root key with ID 66e9aff: Enter passphrase for new root key with ID 66e9aff: Enter passphrase for new root key with ID 66e9aff: Enter passphrase for new root key with ID 66e9aff: maximum number of passphrase attempts exceeded [Pipeline] }
          Hide
          rtyler R. Tyler Croy added a comment -

          Fixed this by removing the unnecessary workflow-job plugin version pinning in the Dockerfile

          Show
          rtyler R. Tyler Croy added a comment - Fixed this by removing the unnecessary workflow-job plugin version pinning in the Dockerfile
          Hide
          michaelneale Michael Neale added a comment -

          mashes the keyboard

          Show
          michaelneale Michael Neale added a comment - mashes the keyboard

            People

            Assignee:
            rtyler R. Tyler Croy
            Reporter:
            rtyler R. Tyler Croy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: