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

No automatic builds for tags

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Not A Defect
    • None
    • Jenkins 2.73.2, Git Plugin 3.6.0, Pipeline: Multibranch 2.16

    Description

      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.

       

      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
      

      I expected that a new build is triggered, when a new tag is found. How to achieve this?

       

      Attachments

        Issue Links

          Activity

            pmr Philipp Moeller created issue -
            abayer Andrew Bayer made changes -
            Field Original Value New Value
            Component/s branch-api-plugin [ 18621 ]
            Component/s pipeline [ 21692 ]
            stephenconnolly Stephen Connolly made changes -
            Resolution Not A Defect [ 7 ]
            Status Open [ 1 ] Resolved [ 5 ]
            stephenconnolly Stephen Connolly made changes -
            Attachment build-tags.gif [ 43729 ]
            stephenconnolly Stephen Connolly made changes -
            markewaite Mark Waite made changes -
            Link This issue is related to JENKINS-53432 [ JENKINS-53432 ]
            wcurry Will Curry made changes -
            Description 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?

             
             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?

             
            baymac Parichay Barpanda made changes -
            Link This issue is related to JENKINS-58477 [ JENKINS-58477 ]
            markewaite Mark Waite made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            mint_tamas Tamás made changes -
            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.  ]

            People

              markewaite Mark Waite
              pmr Philipp Moeller
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: