|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I am able to duplicate the bug. I can't currently explain (without debugger, etc.) why that "branch to build" definition with the leading colon (":origin/release-\d{8}") is passed to git rev-parse, since git rev-parse is not used to process regular _expression_ based branch name matching.
I also confirmed your work around of using ":origin/release-\d*" and an alternate work around using ":origin/release-\d{8}.*". Those are both only work arounds to the bug, since the trailing "{8}" is a perfectly valid syntax as far as I can tell.
As your test shows, the problem does not seem to be in the BranchSpec matcher, but somewhere else in the plugin where it is deciding that it should not use the regular _expression_ based branch name matcher, or it is failing a git rev-parse call prior to the branch name matching step.