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

Git plugin: tags & triggers don't work as expected

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: git-plugin
    • Labels:
      None
    • Environment:
      Fedora 17 64bit
    • Similar Issues:

      Description

      I trigger Jenkins from a post-receive hook on my git server:
      curl -s "${jenkinsUrl}/git/notifyCommit?url=${cloneUrl}"

      When I push a (annotated) tag on the latest commit that Jenkins has already built, no new build is started.
      Since the commit sha of the branch to build doesn't change that's logical.

      However, since I use 'git describe' to provide traceability of my artifacts, this is not what I'd like to happen: the 'git describe' output actually changes because of the new tag.

      To fix this, the git plugin must not only look at the commit sha but also check the tags on the latest commit that it has built; if there is a new/changed tag on that commit, a new build has to be started.

        Attachments

          Issue Links

            Activity

            Hide
            sschuberth Sebastian Schuberth added a comment -

            Seems like this duplicates JENKINS-14917.

            Show
            sschuberth Sebastian Schuberth added a comment - Seems like this duplicates JENKINS-14917 .
            Hide
            jbq jbq added a comment -
            Show
            jbq jbq added a comment - Fixed, see https://github.com/jenkinsci/git-plugin/pull/340

              People

              • Assignee:
                jbq jbq
                Reporter:
                fhuberts Ferry Huberts
              • Votes:
                2 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: