[
https://issues.jenkins-ci.org/browse/JENKINS-9159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162398#comment-162398
]
Carl Norum commented on JENKINS-9159:
-------------------------------------
I'm just starting with Jenkins, but this one bit me; having to maintain the
"pretty version" in two places seems prone to error. Certainly there's an easy
workaround, but it would be good for it to behave nicely.
> use a parameter value or an environment value for setting the build name
> build-name-setter-plugin
> -------------------------------------------------------------------------------------------------
>
> Key: JENKINS-9159
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9159
> Project: Jenkins
> Issue Type: Bug
> Components: build-name-setter
> Reporter: farshidce
>
> the set build description plugin allows the user to use one of the env
> variables or the job's parameter in setting the description.the
> build-name-setter-plugin doesn't accept such parameter though.
> ideally we can have one plugin that let the user to set the build_name and
> build_description.
> this is not a core bug but i couldn't find a component for
> build-name-setter-plugin
--
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
