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

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

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • git-plugin
    • None
    • Fedora 17 64bit

      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.

          [JENKINS-17898] Git plugin: tags & triggers don't work as expected

          Ferry Huberts created issue -
          Ferry Huberts made changes -
          Description Original: I trigger Jenkins from a post-receive hook on my git server:
            curl -s "${jenkinsUrl}/git/notifyCommit?url=${cloneUrl}"

          When I push a tag on the latest commit that Jenkins has already built, no new built 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.
          New: I trigger Jenkins from a post-receive hook on my git server:
            curl -s "${jenkinsUrl}/git/notifyCommit?url=${cloneUrl}"

          When I push a 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.
          Ferry Huberts made changes -
          Description Original: I trigger Jenkins from a post-receive hook on my git server:
            curl -s "${jenkinsUrl}/git/notifyCommit?url=${cloneUrl}"

          When I push a 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.
          New: 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.
          Mark Waite made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          Sebastian Schuberth made changes -
          Link New: This issue duplicates JENKINS-14917 [ JENKINS-14917 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 149194 ] New: JNJira + In-Review [ 177278 ]
          Mark Waite made changes -
          Link New: This issue is duplicated by JENKINS-38921 [ JENKINS-38921 ]
          jbq made changes -
          Assignee Original: Nicolas De Loof [ ndeloof ] New: jbq [ jbq ]
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Mark Waite made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

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

              Created:
              Updated:
              Resolved: