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

Git Plugin fails to resolve tags containing a slash since 2.0.1

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • git-plugin
    • None

      Since updating from 2.0.1 to 2.0.3, a job which uses tags containing a slash as "branch" does not work anymore (rel/x.y.z-... in my case)

      I my case, a sepate job creates a release tag (refs/tags/rel/my-tag).

      The job that stopped to work tries to check out this given tag (using a parameter: so the branch field contains the value: rel/$version)

      Using git plugin 2.0.1, this works. Using git plugin 2.0.3 the checkout attempt results in "Couldn't find any revision to build. Verify the repository and branch configuration for this job."

      Downgrading to 2.0.1 solves the problem.

      The problem has already been discussed in JENKINS-14026, but the applied fix only works for slash-less tags

          [JENKINS-21952] Git Plugin fails to resolve tags containing a slash since 2.0.1

          Stephan Pauxberger created issue -

          Mark Waite added a comment -

          Could you double check that the other bug you reference is the bug you intended to reference? JENKINS-14206 seems unrelated to the git plugin.

          Mark Waite added a comment - Could you double check that the other bug you reference is the bug you intended to reference? JENKINS-14206 seems unrelated to the git plugin.
          Stephan Pauxberger made changes -
          Description Original: Since updating from 2.0.1 to 2.0.3, a job which uses tags containing a slash as "branch" do not work anymore (rel/x.y.z-... in my case)

          Build results in "Couldn't find any revision to build. Verify the repository and branch configuration for this job."

          Downgrading to 2.0.1 solves the problem.

          The problem has already been discussed in [JENKINS-14206], but the applied fix only works for slash-less tags


          		 New: Since updating from 2.0.1 to 2.0.3, a job which uses tags containing a slash as "branch" do not work anymore (rel/x.y.z-... in my case)

          Build results in "Couldn't find any revision to build. Verify the repository and branch configuration for this job."

          Downgrading to 2.0.1 solves the problem.

          The problem has already been discussed in [JENKINS-14026], but the applied fix only works for slash-less tags

          Stephan Pauxberger added a comment -

          Sorry, Typo. Corrected.

          Stephan Pauxberger added a comment - Sorry, Typo. Corrected.
          Stephan Pauxberger made changes -
          Description Original: Since updating from 2.0.1 to 2.0.3, a job which uses tags containing a slash as "branch" do not work anymore (rel/x.y.z-... in my case)

          Build results in "Couldn't find any revision to build. Verify the repository and branch configuration for this job."

          Downgrading to 2.0.1 solves the problem.

          The problem has already been discussed in [JENKINS-14026], but the applied fix only works for slash-less tags


          		 New: Since updating from 2.0.1 to 2.0.3, a job which uses tags containing a slash as "branch" does not work anymore (rel/x.y.z-... in my case)

          Build results in "Couldn't find any revision to build. Verify the repository and branch configuration for this job."

          Downgrading to 2.0.1 solves the problem.

          The problem has already been discussed in [JENKINS-14026], but the applied fix only works for slash-less tags

          Mark Waite added a comment -

          Can you describe how the tags are used?

          Are you using the tags as the branch to checkout, or are you applying tags as part of the build process, or something completely different?

          Mark Waite added a comment - Can you describe how the tags are used? Are you using the tags as the branch to checkout, or are you applying tags as part of the build process, or something completely different?
          Stephan Pauxberger made changes -
          Description Original: Since updating from 2.0.1 to 2.0.3, a job which uses tags containing a slash as "branch" does not work anymore (rel/x.y.z-... in my case)

          Build results in "Couldn't find any revision to build. Verify the repository and branch configuration for this job."

          Downgrading to 2.0.1 solves the problem.

          The problem has already been discussed in [JENKINS-14026], but the applied fix only works for slash-less tags


          		 New: Since updating from 2.0.1 to 2.0.3, a job which uses tags containing a slash as "branch" does not work anymore (rel/x.y.z-... in my case)

          I my case, a sepate job creates a release tag (refs/tags/rel/my-tag).

          The job that stopped to work tries to check out this given tag (using a parameter: so the branch field contains the value: rel/$version)

          Using git plugin 2.0.1, this works. Using git plugin 2.0.3 the checkout attempt results in "Couldn't find any revision to build. Verify the repository and branch configuration for this job."

          Downgrading to 2.0.1 solves the problem.

          The problem has already been discussed in [JENKINS-14026], but the applied fix only works for slash-less tags

          Stephan Pauxberger added a comment -

          updated the description. I try to check out a deep tag (containing a slash) created by another job.

          Stephan Pauxberger added a comment - updated the description. I try to check out a deep tag (containing a slash) created by another job.

          Mark Waite added a comment -

          Thanks. When you reverted back to git-plugin 2.0.1, did you also revert to an earlier version of git-client-plugin, or did you remain with the current release of git-client-plugin (1.6.3)?

          I ask because I'm concerned that the root of the issue might be in git-client-plugin rather than git-plugin. If you only reverted the git-plugin and that was enough to resolve the issue, then the problem is most likely in the git-plugin, not in git-client-plugin.

          Mark Waite added a comment - Thanks. When you reverted back to git-plugin 2.0.1, did you also revert to an earlier version of git-client-plugin, or did you remain with the current release of git-client-plugin (1.6.3)? I ask because I'm concerned that the root of the issue might be in git-client-plugin rather than git-plugin. If you only reverted the git-plugin and that was enough to resolve the issue, then the problem is most likely in the git-plugin, not in git-client-plugin.

          Stephan Pauxberger added a comment -

          I did only revert git-plugin, git-client-plugin is current version.

          Stephan Pauxberger added a comment - I did only revert git-plugin, git-client-plugin is current version.

            ndeloof Nicolas De Loof
            paux Stephan Pauxberger
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: