[JIRA] (JENKINS-14917) Build is not triggered for new tag (without new commit)

[jbq@caraldi.com (JIRA)]

jbq resolved as Fixed

https://github.com/jenkinsci/git-plugin/pull/340 Jenkins / JENKINS-14917 Build is not triggered for new tag (without new commit) Change By: jbq Status: Open Resolved Assignee: Nicolas De Loof jbq Resolution: Fixed Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[g.josquin+jenkins@gmail.com (JIRA)]

Guido Josquin reopened an issue

This is still not working for me, so I am reopening the issue. Description: https://stackoverflow.com/questions/50778526/trigger-a-jenkins-pipeline-by-tagging-an-existing-commit

Jenkins / JENKINS-14917 Build is not triggered for new tag (without new commit)

Change By: Guido Josquin Resolution: Fixed Status: Resolved Reopened Assignee: jbq

Add Comment

[g.josquin+jenkins@gmail.com (JIRA)]

Guido Josquin edited a comment on JENKINS-14917

Re: Build is not triggered for new tag (without new commit)

This is still not working for me, so I am reopening the issue. Description:

[ https://stackoverflow.com/questions/50778526/trigger-a-jenkins-pipeline-by-tagging-an-existing-commit ]   Perhaps you might be able to help, [~jbq] - is tag-triggered building currently supported?

Add Comment

[jbq@caraldi.com (JIRA)]

jbq commented on JENKINS-14917

Re: Build is not triggered for new tag (without new commit)

Hi Guido, I made my work, reviewed, tested and pushed the proposed changes on march 2017.  Now there it is likely that a regression has popped in since then.  Unfortunately I'm not working on Jenkins ATM and can't offer help on this.

Add Comment

[andy.goldstein@gmail.com (JIRA)]

Andy Goldstein commented on JENKINS-14917

Re: Build is not triggered for new tag (without new commit)

As best I can determine, the git plugin filters out "non-tip" revisions, leading to this situation. For example, imagine this flow: Push to master, commit d0253f44158313c249a7db9892f984fd0e8596b2 Jenkins builds that branch/commit Tag master as v1.2.3, which becomes commit 8f0a0c31a89b6a594eeb1e8db6a2fcc4e1923890 Jenkins shows the following (if you enable verbose git output) After branch filtering: [Revision d0253f44158313c249a7db9892f984fd0e8596b2 (origin/master), Revision 8f0a0c31a89b6a594eeb1e8db6a2fcc4e1923890 (origin/tags/v1.2.3)] After non-tip filtering: [Revision d0253f44158313c249a7db9892f984fd0e8596b2 (origin/master)] Removing what's already been built: {origin/master=Build #5 of Revision d0253f44158313c249a7db9892f984fd0e8596b2 (origin/master)} After filtering out what's already been built: [] Nothing seems worth building, so falling back to the previously built revision: Revision d0253f44158313c249a7db9892f984fd0e8596b2 (origin/master) The only way I can think of to build branches vs tags is to have separate jobs for each, which isn't ideal.

Add Comment

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

[andy.goldstein@gmail.com (JIRA)]

Andy Goldstein edited a comment on JENKINS-14917

Re: Build is not triggered for new tag (without new commit)

As best I can determine, the git plugin filters out "non-tip" revisions, leading to this situation. For example, imagine this flow:

# Push to master, commit d0253f44158313c249a7db9892f984fd0e8596b2 # Jenkins builds that branch/commit # Tag master as v1.2.3, which becomes commit 8f0a0c31a89b6a594eeb1e8db6a2fcc4e1923890 # Jenkins shows the following (if you enable verbose git output)

{{ After branch filtering: [Revision d0253f44158313c249a7db9892f984fd0e8596b2 (origin/master), Revision 8f0a0c31a89b6a594eeb1e8db6a2fcc4e1923890 (origin/tags/v1.2.3)] }} {{ After non-tip filtering: [Revision d0253f44158313c249a7db9892f984fd0e8596b2 (origin/master)] }} {{ Removing what's already been built: \{origin/master=Build #5 of Revision d0253f44158313c249a7db9892f984fd0e8596b2 (origin/master)} }} {{ After filtering out what's already been built: [] }} {{ Nothing seems worth building, so falling back to the previously built revision: Revision d0253f44158313c249a7db9892f984fd0e8596b2 (origin/master) }} The only way I can think of to build branches vs tags is to have separate jobs for each, which isn't ideal.

Add Comment

[andy.goldstein@gmail.com (JIRA)]

Andy Goldstein edited a comment on JENKINS-14917

Re: Build is not triggered for new tag (without new commit)

As best I can determine, the git plugin filters out "non-tip" revisions, leading to this situation. For example, imagine this flow: # Push to master, commit d0253f44158313c249a7db9892f984fd0e8596b2 # Jenkins builds that branch/commit # Tag master as v1.2.3, which becomes commit 8f0a0c31a89b6a594eeb1e8db6a2fcc4e1923890 # Jenkins shows the following (if you enable verbose git output)

{ { noformat}

After branch filtering: [Revision d0253f44158313c249a7db9892f984fd0e8596b2 (origin/master), Revision 8f0a0c31a89b6a594eeb1e8db6a2fcc4e1923890 (origin/tags/v1.2.3)] }} {{ After non-tip filtering: [Revision d0253f44158313c249a7db9892f984fd0e8596b2 (origin/master)]}} {{ Removing what's already been built: \

{origin/master=Build #5 of Revision d0253f44158313c249a7db9892f984fd0e8596b2 (origin/master)}}}

{{ After filtering out what's already been built: []}}

{{ Nothing seems worth building, so falling back to the previously built revision: Revision d0253f44158313c249a7db9892f984fd0e8596b2 (origin/master)}} {noformat}

The only way I can think of to build branches vs tags is to have separate jobs for each, which isn't ideal.

Add Comment

[andy.goldstein@gmail.com (JIRA)]

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated JENKINS-14917

Jenkins / JENKINS-14917

Build is not triggered for new tag (without new commit)

Change By: Mark Waite Status: Reopened Open

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)