-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Centos OS 6,
git version 1.7.12.4,
Jenkins ver. 1.588,
GIT plugin 2.2.7
Docs says that ${GIT_BRANCH} macro should expands to the full branch name, such as 'origin/master'. Otherwise(without fullName parameter), it only expands to the short name, such as 'master', but without fullName parameter it expands to 'remotes/origin/master' with fullName parameter it doesn't work at all.
- is related to
-
JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH
-
- Open
-
I can't duplicate the exact problems you're describing. I need more clarification of the steps you're taking, and what you're observing.
The token macro plugin notes that the git plugin is a token producer, and then lists several plugins which are token consumers.
When I use ${GIT_BRANCH} with a token consumer plugin (the build name setter plugin), I can see the following behavior:
When I use ${GIT_BRANCH} with a plugin which is not a token consumer plugin (the XShell plugin), I see the following:
I believe that is an expected result for all the parameterized values, since the XShell plugin does not support token macro parameter expansion.
Can you explain in more detail which plugin you're using to consume the token macro?