|
||||||||||||||
|
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 plugin wiki page documents the current behavior by saying that GIT_BRANCH is the 'name of the remote repository (defaults to origin), followed by name of the branch currently being used, e.g. "origin/master" or "origin/foo"'.
There are now assertions in GitSCMTest which test that the description in the wiki page is correct, by testing that the GIT_BRANCH environment variable is "origin/master".
With those two conditions, I'm reasonably confident that the git plugin 2.0 behavior is the expected current behavior and the intended future behavior.