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

When used as a promotion action, the "Set build description" step is not doing what is expected

    XMLWordPrintable

Details

    Description

      When an action of type "Set build description" is used as a promotion step for a build, let's call it BuildJobABC, it doesn't set the build's description.

      Technically speaking, the promotion step doesn't fail. However, it sets the description of the promotion itself instead of setting the description of the build.

      For example, if BuildJobABC has a promotion named PromoABC which is configured with an action of type "Set build description", the result of running PromoABC would be seen in the file "%JENKINS_HOME%\jobs\BuildJobABC\promotions\PromoABC\builds\PromotionId\build.xml" in the field "/hudson.plugins.promoted__builds.Promotion/actions/hudson.plugins.descriptionsetter.DescriptionSetterAction/description".

      The expected behavior is for the promotion step to set the description of the build. This should be visible in the file "%JENKINS_HOME%\jobs\BuildJobABC\builds\BuildId\build.xml"

      Attachments

        Activity

          I have the same issue using 1.441 with Promoted Builds 2.4 and Description Setter 1.8

          nperrier Nathan Perrier added a comment - I have the same issue using 1.441 with Promoted Builds 2.4 and Description Setter 1.8
          tonioska tonioska added a comment -

          Same issue here with Jenkins 1.450, Promoted Builds 2.4 and Jenkins description setter plugin 1.8.

          tonioska tonioska added a comment - Same issue here with Jenkins 1.450, Promoted Builds 2.4 and Jenkins description setter plugin 1.8.

          Noticed this too. I added the description setter plugin to the components list and made it a "Major" bug because it has not been noticed at all.

          pizzaboy13 Bob The Builder Can He Fix It? added a comment - Noticed this too. I added the description setter plugin to the components list and made it a "Major" bug because it has not been noticed at all.

          I'd love to see this fixed to - currently, we use promotions to re-do a "dev" build into a release and to find out the actual release a dev build because we have to click 3-4 links to get to the actual release job results - it would be nice if the original dev job (where the giold star is) would also show the release version by simply calling the description setter.

          newlix Jean-Serge Gagnon added a comment - I'd love to see this fixed to - currently, we use promotions to re-do a "dev" build into a release and to find out the actual release a dev build because we have to click 3-4 links to get to the actual release job results - it would be nice if the original dev job (where the giold star is) would also show the release version by simply calling the description setter.
          gosha_f Gosha Frost added a comment -

          As workaround you can use Groovy Postbuild action and 'Approval Parameter' RELEASE_VERSION in promotion section

          promotion = manager.build;
          promotion.target.description=promotion.environment.get('RELEASE_VERSION')

          gosha_f Gosha Frost added a comment - As workaround you can use Groovy Postbuild action and 'Approval Parameter' RELEASE_VERSION in promotion section promotion = manager.build; promotion.target.description=promotion.environment.get('RELEASE_VERSION')

          People

            Unassigned Unassigned
            bogdaniosif bogdaniosif
            Votes:
            11 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated: