[JIRA] (JENKINS-14917) Build is not triggered for new tag (without new commit)
Title: Message Title
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
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14917) Build is not triggered for new tag (without new commit)
Title: Message Title
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)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14917) Build is not triggered for new tag (without new commit)
Title: Message Title
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
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14917) Build is not triggered for new tag (without new commit)
Title: Message Title
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
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
