Mark Waite edited a comment on Bug JENKINS-25465

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:

||Input branch||${GIT_BRANCH}||${GIT_BRANCH,fullName=false}||${GIT_BRANCH,fullName=true}||${GIT_BRANCH,all}||
|master|remotes/origin/master|remotes/origin/master|refs/remotes/origin/master|${GIT_BRANCH,all}|

When I use ${GIT_BRANCH} with a plugin which is not a token consumer plugin (the XShell plugin), I see the following:

||Input branch||${GIT_BRANCH}||${GIT_BRANCH,fullName=false}||${GIT_BRANCH,fullName=true}||${GIT_BRANCH,all}||
|master |origin/master |${GIT_BRANCH,fullName=false} |${GIT_BRANCH,fullName=true} |${GIT_BRANCH,all} |

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?

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.

Reply via email to