|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I'd rather say this is a missing feature instead of a bug. In fact, even if setting up the refspec worked that way, it would also trigger builds if some long past commit was tagged that precedes an existing tag in history. But what you usually want is to trigger a build if a new most recent tag with a certain name pattern appears on some branch. The bad news is that "git tag --list" lists tags alphabetically, not in (reverse) chronological order. The good news is that you can use "git log --tags" in conjunction with a special trigger job to achieve the desired effect. I've outlined the details of this approach as part of this answer on StackOverflow.