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

LTS branch does not contain SCM API 2.0.2 release, but depends on it

      I just upgraded to Jenkins 2.32.2 and then to GitHub Branch Source 2.0.1 when prompted, but now it's refusing to load due to a dependency on SCM API 2.0.2 or later. However, the latest version of SCM API on the LTS branch appears to be 1.3 – that's what I have, and no newer version is listed in the Manage Plugins page.

      EDIT: I originally filed this under the scm-api-plugin component but have added github-branch-source-plugin component since the issue relates to both.

          [JENKINS-41661] LTS branch does not contain SCM API 2.0.2 release, but depends on it

          OK, I'll see if that is missing in the zip. until then you can get that from https://jenkins-updates.cloudbees.com/download/plugins/pipeline-github-lib/1.0/pipeline-github-lib.hpi

          Stephen Connolly added a comment - OK, I'll see if that is missing in the zip. until then you can get that from https://jenkins-updates.cloudbees.com/download/plugins/pipeline-github-lib/1.0/pipeline-github-lib.hpi

          What is the sha1sum of the zip that you downloaded?

          $ unzip -l ~/Dropbox/scm-api.zip pipeline-github-lib.jpi
          Archive:  /Users/stephenc/Dropbox/scm-api.zip
            Length      Date    Time    Name
          ---------  ---------- -----   ----
               8479  01-16-2017 17:28   pipeline-github-lib.jpi
          ---------                     -------
               8479                     1 file
          

          Stephen Connolly added a comment - What is the sha1sum of the zip that you downloaded? $ unzip -l ~/Dropbox/scm-api.zip pipeline-github-lib.jpi Archive: /Users/stephenc/Dropbox/scm-api.zip Length Date Time Name --------- ---------- ----- ---- 8479 01-16-2017 17:28 pipeline-github-lib.jpi --------- ------- 8479 1 file

          mkobit See previous question

          Stephen Connolly added a comment - mkobit See previous question

          Mike Kobit added a comment -
          gsha1sum ~/Downloads/scm-api.zip 
          c7b6279f8b8aebf9893bfa35a6c33e0a6537b7ea  /Users/mkobit/Downloads/scm-api.zip
          

          If I unzip it I see that file in there as well, so maybe I screwed something else up.

          Mike Kobit added a comment - gsha1sum ~/Downloads/scm-api.zip c7b6279f8b8aebf9893bfa35a6c33e0a6537b7ea /Users/mkobit/Downloads/scm-api.zip If I unzip it I see that file in there as well, so maybe I screwed something else up.

          Nick Jones added a comment - - edited

          stephenconnolly, I had downgraded back to GitHub Branch Source 1.10.1 to resolve the issue (without attempting to upgrade SCM API to 2.0.2), and it seems to be operational with no warnings or issues. Would the irreversible migration only have occurred if the v2 GitHub Branch Source plugin had actually loaded, and that load was blocked by the out of date SCM API I was/am using?

          I'm currently running the latest versions of all LTS plugins apart from Cobertura (due to JENKINS-30700) and Dashboard (due to JENKINS-35414).

          Nick Jones added a comment - - edited stephenconnolly , I had downgraded back to GitHub Branch Source 1.10.1 to resolve the issue (without attempting to upgrade SCM API to 2.0.2), and it seems to be operational with no warnings or issues. Would the irreversible migration only have occurred if the v2 GitHub Branch Source plugin had actually loaded, and that load was blocked by the out of date SCM API I was/am using? I'm currently running the latest versions of all LTS plugins apart from Cobertura (due to JENKINS-30700 ) and Dashboard (due to JENKINS-35414 ).

          Mike Kobit added a comment -

          I was able to get the unzip to work to with our actual production plugins configuration, but not with the "download list of latest" plugins that I had set up for development.

          Thanks stephenconnolly for the quick response.

          Mike Kobit added a comment - I was able to get the unzip to work to with our actual production plugins configuration, but not with the "download list of latest" plugins that I had set up for development. Thanks stephenconnolly for the quick response.

          David Skowronski added a comment - - edited

          I'm seeing the same problem. I just updated Jenkins:alpine docker container from 2.32.1 to 2.32.2 and only see SCM API plugin version 1.3 available.

          David Skowronski added a comment - - edited I'm seeing the same problem. I just updated Jenkins:alpine docker container from 2.32.1 to 2.32.2 and only see SCM API plugin version 1.3 available.

          medianick Correct, the migration would only have occurred if the plugin had started, because it didn't start your data was not migrated and hence you are fine.

          Stephen Connolly added a comment - medianick Correct, the migration would only have occurred if the plugin had started, because it didn't start your data was not migrated and hence you are fine.

          dskow Currently you should only see SCM API 1.3 available.

          If you have managed to get GitHub Branch Source 2.0.1 installed on your instance due to bad luck when accessing the cache (or similarly with BitBucket Branch Source) you can download the 1.x version from https://jenkins-updates.cloudbees.com/download/plugins/github-branch-source/ (or https://jenkins-updates.cloudbees.com/download/plugins/cloudbees-bitbucket-branch-source/ for bitbucket)

          Specifically you would want https://jenkins-updates.cloudbees.com/download/plugins/github-branch-source/1.10.1/github-branch-source.hpi (or BitBucket people want https://jenkins-updates.cloudbees.com/download/plugins/cloudbees-bitbucket-branch-source/1.9/cloudbees-bitbucket-branch-source.hpi)

          On monday you can safely upgrade all plugins to the 2.0.x lines when we put everything into the update center in one go.

          For more context read the draft of the blog post to go out on Monday here: https://github.com/stephenc/jenkins.io/blob/ff6002e76c664dc71738d3ceb19273f3bc5c830b/content/blog/2017/2017-02-06-scm-api-2-take2.adoc

          Stephen Connolly added a comment - dskow Currently you should only see SCM API 1.3 available. If you have managed to get GitHub Branch Source 2.0.1 installed on your instance due to bad luck when accessing the cache (or similarly with BitBucket Branch Source) you can download the 1.x version from https://jenkins-updates.cloudbees.com/download/plugins/github-branch-source/ (or https://jenkins-updates.cloudbees.com/download/plugins/cloudbees-bitbucket-branch-source/ for bitbucket) Specifically you would want https://jenkins-updates.cloudbees.com/download/plugins/github-branch-source/1.10.1/github-branch-source.hpi (or BitBucket people want https://jenkins-updates.cloudbees.com/download/plugins/cloudbees-bitbucket-branch-source/1.9/cloudbees-bitbucket-branch-source.hpi ) On monday you can safely upgrade all plugins to the 2.0.x lines when we put everything into the update center in one go. For more context read the draft of the blog post to go out on Monday here: https://github.com/stephenc/jenkins.io/blob/ff6002e76c664dc71738d3ceb19273f3bc5c830b/content/blog/2017/2017-02-06-scm-api-2-take2.adoc

          ok I'll wait till Monday thanks.

          David Skowronski added a comment - ok I'll wait till Monday thanks.

            stephenconnolly Stephen Connolly
            medianick Nick Jones
            Votes:
            10 Vote for this issue
            Watchers:
            27 Start watching this issue

              Created:
              Updated:
              Resolved: