Hi Bob,
I was just encountering this problem today. Try specifying the build
name as
#${ENV,var="BUILD_NUMBER"} ${ENV,var="GIT_BRANCH_OR_TAG"}
I found this suggestion in a Jenkins bug reportJENKINS-13347
<https://issues.jenkins-ci.org/browse/JENKINS-13347>.
Eric
On 6/20/2013 1:54 PM, Bob Bick wrote:
Hi,
Newbie question here...
I am attempting to use the BuildNameSetter plugin to set the Jenkins build name to an
input parameter. Specifically, my job has a parameter named "GIT_BRANCH_OR_TAG".
I set the Build Name to:
#${BUILD_NUMBER} ${GIT_BRANCH_OR_TAG}
Which results in:
Unrecognized macro 'GIT_BRANCH_OR_TAG' in '#${BUILD_NUMBER}
${GIT_BRANCH_OR_TAG}'
I am sure I am doing something stupid; but, not sure how this could be
happening.
Any ideas?
Thanks for taking the time to read this.
Bob
*** *** ***
This message contains information which may be confidential and privileged.
Unless you are the addressee (or authorized to receive for the addressee), you
may not use, copy or disclose to anyone the message or any information
contained in the message. If you have received the message in error, please
advise the sender by reply e-mail and delete the message.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
