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

Unable to install bitbucket-branch-source 2.0.2 due to broken dependency

      Maybe related to JENKINS-41661, but I'm not using the LTS branch. I have added the experimental update center for blueocean betas, and from there I have SCM API plugin 2.0.2-beta-2. Now I can't install bitbucket-branch-source 2.0.2:

      java.io.IOException: Bitbucket Branch Source Plugin v2.0.2 failed to load.

      • SCM API Plugin v2.0.2-beta-2 is older than required. To fix, install v2.0.2 or later.
        at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:621)
        at hudson.PluginManager.dynamicLoad(PluginManager.java:864)
        Caused: java.io.IOException: Failed to install cloudbees-bitbucket-branch-source plugin
        at hudson.PluginManager.dynamicLoad(PluginManager.java:874)
        at hudson.PluginManager.dynamicLoad(PluginManager.java:814)
        at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1891)
        Caused: java.io.IOException: Failed to dynamically deploy this plugin
        at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1895)
        at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1652)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
        at java.lang.Thread.run(Thread.java:745)

      Is there a scm api plugin 2.0.2 released, and if so why can't I update to it (I can't see that version at all in the update center)?

          [JENKINS-41705] Unable to install bitbucket-branch-source 2.0.2 due to broken dependency

          Emil Styrke added a comment -

          I have now read the thread at JENKINS-41661, and I am more confident that this is related. I will wait until monday when the plugins are released - this is not urgent for the weekend.

          Emil Styrke added a comment - I have now read the thread at JENKINS-41661 , and I am more confident that this is related. I will wait until monday when the plugins are released - this is not urgent for the weekend.

          Tim Payne added a comment -

          https://updates.jenkins-ci.org/download/plugins/scm-api/ does not currently contain anything above v1.3.

          This is causing lots of plugin dependency errors!

          Tim Payne added a comment - https://updates.jenkins-ci.org/download/plugins/scm-api/ does not currently contain anything above v1.3. This is causing lots of plugin dependency errors!

          Andrei Costescu added a comment - - edited

          I got the same problem after doing a routine upgrade last week on the standard stable jenkins 2.x build. Now it always complains in "Manage Jenkins" that:

          There are dependency errors loading some plugins: 
          GitHub Branch Source Plugin v2.0.1 
          SCM API Plugin v1.3 is older than required. To fix, install v2.0.2 or later.
          GitHub Organization Folder Plugin v1.5 
          GitHub Branch Source Plugin v1.9 failed to load. Fix this plugin first.

          And indeed the plugin's page lists 1.3 as latest. I can't upgrade the plugin. And can't downgrade the other plugins either nicely because they fail to load. I could manually remove the plugins from disk but I prefer waiting for a compatible version of SCM API plugin.

          Andrei Costescu added a comment - - edited I got the same problem after doing a routine upgrade last week on the standard stable jenkins 2.x build. Now it always complains in "Manage Jenkins" that: There are dependency errors loading some plugins: GitHub Branch Source Plugin v2.0.1 SCM API Plugin v1.3 is older than required. To fix, install v2.0.2 or later. GitHub Organization Folder Plugin v1.5 GitHub Branch Source Plugin v1.9 failed to load. Fix this plugin first. And indeed the plugin's page lists 1.3 as latest. I can't upgrade the plugin. And can't downgrade the other plugins either nicely because they fail to load. I could manually remove the plugins from disk but I prefer waiting for a compatible version of SCM API plugin.

          Emil Styrke added a comment -

          Emil Styrke added a comment - costescuandrei : The GitHub issue was due to a typo - see https://issues.jenkins-ci.org/browse/JENKINS-41661?focusedCommentId=286164&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-286164 for background and how to fix it.

          Thanks. I will try that.

          Andrei Costescu added a comment - Thanks. I will try that.

          Should have been fixed by the 2.0.3 release (recommend using the 2.1.0 release as that fixes the critical issue all previous versions had whereby they would delete everything if there was an API error)

          Stephen Connolly added a comment - Should have been fixed by the 2.0.3 release (recommend using the 2.1.0 release as that fixes the critical issue all previous versions had whereby they would delete everything if there was an API error)

            amuniz Antonio Muñiz
            estyrke Emil Styrke
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: