|
||||||||
|
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.
The git-client-plugin 1.10.0 release will include a change which allows the job to specify branch names more precisely. So that we don't break compatibility with existing job definitions, the more specific branch name needs to use a different string.
Plugin versions prior to 1.10.0 typically used "Branch to build" arguments like "origin/master" or "/develop". Those values had all text left of the right-most slash removed, then the remaining text was used to match branch names. That allowed multiple branches to match a single "branch to build", even if that was not the intention of the job definer. It did not allow precise specification of a single branch, especially when namespaces were used. In your example, it caused "jdoe/blah/festivus-dev" and "festivus-dev" to both match.
That form of "branch to build" is still supported, but now the "Branches to build" also accepts arguments like "refs/heads/origin/master" and "refs/heads/origin//develop". The "refs/heads" format allows precise specification of the branch to build, without breaking backward compatibility.
In your case, you'd specify the branch to build as "refs/heads/festivus-dev".
Would you be willing to try a pre-release version of 1.10.0 to confirm it fixes your issue?