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

"No version master found for library" after upgrade to 2.3.0

    Details

    • Similar Issues:

      Description

      After upgrading to github branch source plugin version 2.3.0, my global pipeline library failed with the message "ERROR: No version master found for library XXX". Works fine with 2.2.6 both before upgrading and after rolling back the plugin.

        Attachments

          Issue Links

            Activity

            Hide
            stephenconnolly Stephen Connolly added a comment -

            I think 

            https://github.com/jenkinsci/github-branch-source-plugin/pull/167 will fix this.

             

            To confirm, can you check that your pipeline shared library definition does not contain "Discover Branches" and with 2.3.0 when you add "Discover Branches" it starts working again?

             

            If confirmed, then I will merge and release the change in PR#167

            Show
            stephenconnolly Stephen Connolly added a comment - I think  https://github.com/jenkinsci/github-branch-source-plugin/pull/167 will fix this.   To confirm, can you check that your pipeline shared library definition does not contain "Discover Branches" and with 2.3.0 when you add "Discover Branches" it starts working again?   If confirmed, then I will merge and release the change in PR#167
            Hide
            stephenconnolly Stephen Connolly added a comment -

            Assigning to Paul Milliken so he can report results of assessing my theory as to the bug. Please assign it back to me when you have the results

            Show
            stephenconnolly Stephen Connolly added a comment - Assigning to Paul Milliken so he can report results of assessing my theory as to the bug. Please assign it back to me when you have the results
            Hide
            pmilliken Paul Milliken added a comment -

            Stephen Connolly - Confirmed.

            My global pipeline config did not have any additional behaviours defined. I added the discover branches option (set to all) and then re-upgraded the plugin and it works.

            I presume that with the fix the config change won't be necessary (but I suspect won't cause problems either)?

            Show
            pmilliken Paul Milliken added a comment - Stephen Connolly - Confirmed. My global pipeline config did not have any additional behaviours defined. I added the discover branches option (set to all) and then re-upgraded the plugin and it works. I presume that with the fix the config change won't be necessary (but I suspect won't cause problems either)?
            Hide
            stephenconnolly Stephen Connolly added a comment -

            with the fix the config change won't be necessary (but won't cause problems either)

             

            thanks, merging and releasing

            Show
            stephenconnolly Stephen Connolly added a comment - with the fix the config change won't be necessary (but won't cause problems either)   thanks, merging and releasing
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Stephen Connolly
            Path:
            src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java
            http://jenkins-ci.org/commit/github-branch-source-plugin/6d33fbacb140dbf711eec40f7bba161f230378db
            Log:
            [FIXED JENKINS-47902] I think this is the fix

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/6d33fbacb140dbf711eec40f7bba161f230378db Log: [FIXED JENKINS-47902] I think this is the fix
            Hide
            stephenconnolly Stephen Connolly added a comment -

            Fix in GitHub Branch Source 2.3.1, released today (allow time for the update centers to resync or use the workaround above)

            Show
            stephenconnolly Stephen Connolly added a comment - Fix in GitHub Branch Source 2.3.1, released today (allow time for the update centers to resync or use the workaround above)

              People

              • Assignee:
                stephenconnolly Stephen Connolly
                Reporter:
                pmilliken Paul Milliken
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: