-
Bug
-
Resolution: Unresolved
-
Major
-
None
In our company we have always 2 build jobs for each project. One job is working on the HEAD of the repository to trigger e-mails on broken builds and the second job is to publish released versions(tags).
The second job is just checking the repository for tags and publishs the tag builds to the QM department. I have setup this job to watch nightly to the repository and start the job if there is something new. If there is a new commit (+ tag) in the repo, everything works fine. But if there is only a new tag (on a commit which was already built), the job is not started automatically (but only for the next commit).
I tried to setup the refspec to "+refs/heads/:refs/remotes/origin/" or "+refs/heads/:refs/remotes/origin/" but both doesn't work.
Steps to reproduce:
1. set built-trigger to request version control at: * * * * * (to trigger each minute)
2. in git: commit, create a tag, push -> built is started within the next minute -> OK
3. in git: create a tag (on last commit), push -> built is not triggered (expected result: build job should start within the next minute) -> not OK
I'm not sure if this is a bug or something wrong in my configuration.
- duplicates
-
JENKINS-9713 Poll and match tags on top of branches
- Closed
- is duplicated by
-
JENKINS-38921 Jenkins tag based build triggering works inconsistently
- Closed
-
JENKINS-17898 Git plugin: tags & triggers don't work as expected
- Closed