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

Shared libraries stopped loading with git tags. They only now work when I reference a git branch name

    XMLWordPrintable

Details

    Description

      I have a shared library in my Jenkins server that I call "common-pipelines". From within my Jenkinsfile, I will call for a specific tagged version of the common-pipelines shared library to be loaded like this:

      @Library('common-pipelines@v9.4.4') _ 

      I was just alerted that the pipelines are erroring with the following message:

      Please make sure you have the correct access rights
      and the repository exists. 

      However, we aren't sure what changed. After much sanity checking, I was able to determine that this works normally if I call for a branch name rather than a github release (git tag).

      In other words, this works just fine:

       @Library('common-pipelines@myBranchName') _ 

      I am running the latest plugins.

      Attachments

        Issue Links

          Activity

            markewaite Mark Waite added a comment -

            svanoort I won't have time to investigate this further until the weekend at the earliest. I assume you were looking for someone to duplicate the problem as described by the original reporter in order to confirm that the critical change which shows the problem is the update from 2.130 to 2.133.

            piratejohnny are you running Jenkins from a Docker image? If so, are you running from the Alpine Linux docker image?

            The Jenkins base Alpine image switched to Alpine 3.8 recently. That switched the OpenSSH version provided with that Docker image from a prior OpenSSH to OpenSSH 7.7. OpenSSH 7.7 made an intentional change in behavior which broke the Jenkins git client plugin as described in JENKINS-50573. It is remotely possible that this might be another case of the OpenSSH 7.7 change impacting a use case I had not detected previously.

            markewaite Mark Waite added a comment - svanoort I won't have time to investigate this further until the weekend at the earliest. I assume you were looking for someone to duplicate the problem as described by the original reporter in order to confirm that the critical change which shows the problem is the update from 2.130 to 2.133. piratejohnny are you running Jenkins from a Docker image? If so, are you running from the Alpine Linux docker image? The Jenkins base Alpine image switched to Alpine 3.8 recently. That switched the OpenSSH version provided with that Docker image from a prior OpenSSH to OpenSSH 7.7. OpenSSH 7.7 made an intentional change in behavior which broke the Jenkins git client plugin as described in JENKINS-50573 . It is remotely possible that this might be another case of the OpenSSH 7.7 change impacting a use case I had not detected previously.
            piratejohnny Jon B added a comment -

            markewaite Indeed I am running Jenkins via the alpine docker image.

            piratejohnny Jon B added a comment - markewaite Indeed I am running Jenkins via the alpine docker image.
            markewaite Mark Waite added a comment -

            piratejohnny could you download the git client plugin 2.7.3 pre-release to check if it resolves the issue for you? If so, then this is not a core regression but a duplicate of JENKINS-50573.

            markewaite Mark Waite added a comment - piratejohnny could you download the git client plugin 2.7.3 pre-release to check if it resolves the issue for you? If so, then this is not a core regression but a duplicate of JENKINS-50573 .
            markewaite Mark Waite added a comment -

            Included in git client plugin 2.7.3 and git client plugin 3.0.0-beta4 released 24 July 2018.

            markewaite Mark Waite added a comment - Included in git client plugin 2.7.3 and git client plugin 3.0.0-beta4 released 24 July 2018.
            piratejohnny Jon B added a comment -

            git client plugin 2.7.3 seems to resolve the issue under Jenkins 2.133 for my case

            piratejohnny Jon B added a comment - git client plugin 2.7.3 seems to resolve the issue under Jenkins 2.133 for my case

            People

              Unassigned Unassigned
              piratejohnny Jon B
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: