Description
I have Jenkins (2.126) set up to build a pipeline when a new tag is pushed. Specifically, I want to tag an existing commit on master
as release-3
and have it trigger a build. According to several sources, what I want is possible:
https://mohamicorp.atlassian.net/wiki/spaces/DOC/pages/136740885/Triggering+Jenkins+Based+on+New+Tags
Unfortunately, nothing happens when I tag an existing commit and push it to the Git repository. Other builds (triggered by branches) work as expected, and the tag-triggered build in question completes successfully when started manually.
According to some, tag-triggered pipelines should work since version 2.3. Is there anything I can configure to make it work?
Screenshots of attempts
Attempt with a normal pipeline polling at * * * * *
:
Attempt with a multibranch pipeline, scanning every 1 minute
:
Related issues
I found the following issues related to the problem, which is supposed to be resolved.
- https://issues.jenkins-ci.org/browse/JENKINS-38921
- https://issues.jenkins-ci.org/browse/JENKINS-34176
- https://issues.jenkins-ci.org/browse/JENKINS-14917
- https://issues.jenkins-ci.org/browse/JENKINS-47077
- https://issues.jenkins-ci.org/browse/JENKINS-47891
- https://issues.jenkins-ci.org/browse/JENKINS-52376