[
https://issues.jenkins-ci.org/browse/JENKINS-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
evernat resolved JENKINS-9510.
------------------------------
Resolution: Fixed
The pull request was merged in master a year ago:
https://github.com/jenkinsci/git-plugin/commit/7530bc9459fa653482d90ee248b5c74d5bd92b76
So this is fixed.
> GIT_BRANCH token macro non-fullName parses branch incorrectly
> -------------------------------------------------------------
>
> Key: JENKINS-9510
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9510
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Affects Versions: current
> Reporter: Chris Griego
> Assignee: abayer
> Priority: Minor
>
> We use an often ignored feature of git branches where we include "/"
> characters to show a hierarchy, such as "origin/releases/2011/5". The git
> plugin supports this well overall, except for the GIT_BRANCH token macro,
> which if you don't specify fullName reduces it to "5" instead of
> "releases/2011/5". The GIT_BRANCH token macro should strip off the repository
> name only and not everything before the last slash.
> Below is where the full git ref spec is documented.
> http://www.kernel.org/pub/software/scm/git/docs/git-check-ref-format.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
