Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-9159

use a parameter value or an environment value for setting the build name build-name-setter-plugin

      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

          [JENKINS-9159] use a parameter value or an environment value for setting the build name build-name-setter-plugin

          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.

          Ruth Morgenstein added a comment - 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.

          Carl Norum added a comment -

          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.

          Carl Norum added a comment - 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.

          centic added a comment -

          Seems to be the same issue as JENKINS-13347, there the following workaround is given, which I could verify locally as well:

          instead of ${BUILD_NAME}, specify ${ENV,var="BUILD_NAME"}

          centic added a comment - Seems to be the same issue as JENKINS-13347 , there the following workaround is given, which I could verify locally as well: instead of ${BUILD_NAME}, specify ${ENV,var="BUILD_NAME"}

          Pooja Thaker added a comment -

          It is currently possible to pass environment variables to the build name setter plgun. But not build parameter values. I am using the Parameterized Trigger plugin and have some parameters defined for my job. I would like to have the value of one of those build parameters in the build name.

          Pooja Thaker added a comment - It is currently possible to pass environment variables to the build name setter plgun. But not build parameter values. I am using the Parameterized Trigger plugin and have some parameters defined for my job. I would like to have the value of one of those build parameters in the build name.

            le0 Lev Mishin
            farshidce farshidce
            Votes:
            9 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: