[
https://issues.jenkins-ci.org/browse/JENKINS-9159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159350#comment-159350 ]
Ruth Morgenstein commented on JENKINS-9159:
-------------------------------------------
I have a 2-step job chain:
Step 1 - git checkout & build
Step 2 - unit tests
I pass the GIT_BRANCH as a parameter to the test job and want to use the buld-name-setter in the 2nd job, but this bugs prevents it. I've worked around this bug by doing a throw-away git checkout (to set GIT_BRANCH) using the passed branch name, but it would be nice if I didn't have to add this unneeded step.
> 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.jspaFor more information on JIRA, see:
http://www.atlassian.com/software/jira
Locked
