|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I don't intend to change the 2.0 behavior of the GIT_BRANCH variable as returned by the plugin. It includes the remote and the branch name as described by the entry on the wiki page. Unit tests were added a year ago to assure that behavior would be retained across versions of the plugin.
If someone wants to submit a pull request for an additional variable which contains the branch name without the remote, I'm willing to evaluate that. The pull request should include unit tests which confirm the behavior of the new variable. If such a pull request is submitted, it must not change the behavior of the existing GIT_BRANCH variable.