• Type: Bug
• Resolution: Not A Defect
• Priority: Minor
• Component/s: branch-api-plugin, git-plugin
• Labels:

  None
• Environment:

  Jenkins 2.73.2, Git Plugin 3.6.0, Pipeline: Multibranch 2.16

1. 

   Screen Shot 2018-08-14 at 00.41.53.png

   142 kB

   2018-08-13 23:42

2. 

   build-tags.gif

   83 kB

   2018-08-13 23:39

[JENKINS-47496] No automatic builds for tags

Philipp Moeller created issue - 2017-10-18 11:17

Andrew Bayer made changes - 2017-10-20 07:50

Component/s		New: branch-api-plugin [ 18621 ]
Component/s	Original: pipeline [ 21692 ]

Stephen Connolly made changes - 2017-10-23 20:39

Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Stephen Connolly made changes - 2018-08-13 23:39

Attachment

New: build-tags.gif [ 43729 ]

Stephen Connolly made changes - 2018-08-13 23:42

Attachment

New: Screen Shot 2018-08-14 at 00.41.53.png [ 43730 ]

Mark Waite made changes - 2018-09-12 16:09

Link

New: This issue is related to JENKINS-53432 [ JENKINS-53432 ]

Will Curry made changes - 2019-06-25 21:20

Description

Original: After upgrading to the Git Plugin 3.6.0 I activated the "Discover Tags" option in a Multibranch Pipeline Job. The tag is also discovered as expected, but no build is triggered.   {code:java} Checking tags... Checking tag PNR-12345 ‘Jenkinsfile’ found Met criteria Changes detected: PNR-12345 (null → d56c6578f5f04403f4bd64bf2647f3dd0f36e826) No automatic builds for PNR-12345  Processed 1 tags {code} I expected that a new build is triggered, when a new tag is found. How to achieve this?

New:  After upgrading to the Git Plugin 3.6.0 I activated the "Discover Tags" option in a Multibranch Pipeline Job. The tag is also discovered as expected, but no build is triggered.   {code:java} Checking tags... Checking tag PNR-12345 ‘Jenkinsfile’ found Met criteria Changes detected: PNR-12345 (null → d56c6578f5f04403f4bd64bf2647f3dd0f36e826) No automatic builds for PNR-12345  Processed 1 tags {code} I expected that a new build is triggered, when a new tag is found. How to achieve this?

Parichay Barpanda made changes - 2019-07-18 04:21

Link

New: This issue is related to JENKINS-58477 [ JENKINS-58477 ]

Mark Waite made changes - 2019-10-23 01:28

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]

Tamás made changes - 2022-10-28 13:14

Comment

[ It is baffling to me how this basic functionality is not part of Jenkins. The "build storm" issue could easily be avoided. Even the recommended plugin has options to filter tags based on age, but you could even ignore all tags that were created before the feature was enabled in an installation. Lucky we have the "El Oyente" (yes, that's the actual name) pipeline trigger that runs builds based on XMPP pub/sub events. But no builds triggered by tags because that is somehow an unsolvable problem for Jenkins, unlike any CI in existence.  ]