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

Using a Tag in Branch Specifier causes the polling to not detect the head revision

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • git-plugin
    • None
    • Jenkins 1.584
      Jenkins Git Plugin 2.3.1
      Jenkins Multiple SCMs plugin 0.3

      1. Use a Tag in the Branch Specifier.
      2. Polling on the remote repo will occur.
      3. It will run git ls-remote -h MY_REMOTE MY_TAG
      4. This will result in nothing returned from the remote repository.

      git ls-remote has a --tags option which will return the SHA of the Tag.

      Polling is enabled because the Job also checkouts an SVN repository using the Jenkins Multiple SCMs plugin which doesn't refer to a tag.

          [JENKINS-26314] Using a Tag in Branch Specifier causes the polling to not detect the head revision

          Mark Waite added a comment -

          If you force polling to use a workspace, does it resolve the problem?

          Mark Waite added a comment - If you force polling to use a workspace, does it resolve the problem?

          Nathan Smith added a comment -

          Enabling 'force polling using workspace' does seem to workaround the issue thanks.
          Do you agree that this should still be considered a bug since some plugin users would encounter still encounter JENKINS-10131?

          Nathan Smith added a comment - Enabling 'force polling using workspace' does seem to workaround the issue thanks. Do you agree that this should still be considered a bug since some plugin users would encounter still encounter JENKINS-10131 ?

          Mark Waite added a comment -

          nathan_smith it is still a bug.

          Mark Waite added a comment - nathan_smith it is still a bug.

          Jan Klass added a comment -

          Is this bug the cause for the following issue?

          Through defining the refspec we fetch tags into the local branches directory, so we can build any release tags with a branch-wildcard-trigger.
          Occasionaly, a tag will be built again. It seems to only be the second most recent one though, when the most recent one is built after a notify-trigger.

          Jan Klass added a comment - Is this bug the cause for the following issue? Through defining the refspec we fetch tags into the local branches directory, so we can build any release tags with a branch-wildcard-trigger. Occasionaly, a tag will be built again. It seems to only be the second most recent one though, when the most recent one is built after a notify-trigger.

            Unassigned Unassigned
            nathan_smith Nathan Smith
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: