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

description setter postbuild step pollutes build history in matrix projects

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Labels:
      None
    • Environment:
      description-setter-plugin 1.10 with jenkins 1.607
    • Similar Issues:

      Description

      In a matrix project there is an option in the postbuild step to set the build-description in the parent build. The documentation says

      Also set the description on a multi-configuration build. The first
      description found for any of the invididual builds will be used as
      description for the multi-configuration build.
      This only applies to multi-configuration projects.

      I set the build description to the actual git-branch built. With v1.10 now this information is shown as often as configurations are used.

      This is not what I'm expecting, the description text should be there only once (as documented).

      This my be related to JENKINS-26671

        Attachments

          Issue Links

            Activity

            Hide
            samapico Samuel Delisle added a comment -

            In my setup, I was using a build step before the actual compiling to set the version number as description early in the process. Then, I still had to add a post-build step to add that same description to the matrix parent. With 1.10, this caused a whole lot of polluting as described here, both in configuration builds and the matrix parent.

            I think the "append" behavior should be toggleable, as I don't think it is the expected behavior in all cases.

            Show
            samapico Samuel Delisle added a comment - In my setup, I was using a build step before the actual compiling to set the version number as description early in the process. Then, I still had to add a post-build step to add that same description to the matrix parent. With 1.10, this caused a whole lot of polluting as described here, both in configuration builds and the matrix parent. I think the "append" behavior should be toggleable, as I don't think it is the expected behavior in all cases.
            Hide
            pajasoft Pavel Janoušek added a comment -

            Hello,

            I've tried to improve current un-happy situation in JENKINS-30167. It probably can solve your use-case, but sure it isn't an optimal state yet.

            I have a couple of another ideas how to improve the plug-in, but it will be a subject of other JIRAs.

            Show
            pajasoft Pavel Janoušek added a comment - Hello, I've tried to improve current un-happy situation in JENKINS-30167 . It probably can solve your use-case, but sure it isn't an optimal state yet. I have a couple of another ideas how to improve the plug-in, but it will be a subject of other JIRAs.
            Hide
            almahajan Alokkumar Mahajan added a comment - - edited

            Hello,
            Not sure if its related but i see a weird issue when i use Description Setter as part of Post Build step (using Post-Build Script Plug-in), but its only working if the Build is successful. From the logs i see, for failed builds description-setter is not called. I have two steps as part of Post Build first one is Windows batch command which executes a Python utility and second is the Set Build Description.
            Also, i have unchecked the "Execute script only if build succeeds" option.

            I am using Jenkins v 2.10, Description Setter v1.10 and Post-Build Script Plug-in v0.17

            Any comments on this please?

            Thanks..

            Show
            almahajan Alokkumar Mahajan added a comment - - edited Hello, Not sure if its related but i see a weird issue when i use Description Setter as part of Post Build step (using Post-Build Script Plug-in), but its only working if the Build is successful. From the logs i see, for failed builds description-setter is not called. I have two steps as part of Post Build first one is Windows batch command which executes a Python utility and second is the Set Build Description. Also, i have unchecked the "Execute script only if build succeeds" option. I am using Jenkins v 2.10, Description Setter v1.10 and Post-Build Script Plug-in v0.17 Any comments on this please? Thanks..
            Hide
            pajasoft Pavel Janoušek added a comment -

            Alokkumar Mahajan, I don't have an idea how you set your description via Descriptor Setter plug-in in Post-Build Script plug-in, but did you construct the right setup for failed case too? The Descriptor setter plug-in has different description for passed builds and for failed builds. There are two internal attributes for that.

            Show
            pajasoft Pavel Janoušek added a comment - Alokkumar Mahajan , I don't have an idea how you set your description via Descriptor Setter plug-in in Post-Build Script plug-in, but did you construct the right setup for failed case too? The Descriptor setter plug-in has different description for passed builds and for failed builds. There are two internal attributes for that.
            Hide
            almahajan Alokkumar Mahajan added a comment -

            Pavel Janoušek Actually for the Set Description editor shown under post-build script executor plugin, there is no option for Regex for failed build as it is available as part of Post build actions in Advance option for Set Description Setter..

            Show
            almahajan Alokkumar Mahajan added a comment - Pavel Janoušek Actually for the Set Description editor shown under post-build script executor plugin, there is no option for Regex for failed build as it is available as part of Post build actions in Advance option for Set Description Setter..
            Hide
            pajasoft Pavel Janoušek added a comment -

            Alokkumar Mahajan Thank you for your explanation.

            In that case I'd say there is probably an issue on PostBuildScript Plugin side, not on Description Setter Plugin.

            The issue should be reported against the PostBuildScript Plugin component.

            Show
            pajasoft Pavel Janoušek added a comment - Alokkumar Mahajan Thank you for your explanation. In that case I'd say there is probably an issue on PostBuildScript Plugin side, not on Description Setter Plugin . The issue should be reported against the PostBuildScript Plugin component.
            Hide
            almahajan Alokkumar Mahajan added a comment - - edited

            Thanks, I have added my comment @ https://issues.jenkins-ci.org/browse/JENKINS-15395

            Show
            almahajan Alokkumar Mahajan added a comment - - edited Thanks, I have added my comment @ https://issues.jenkins-ci.org/browse/JENKINS-15395

              People

              • Assignee:
                huybrechts huybrechts
                Reporter:
                felixschwitzer felix schwitzer
              • Votes:
                2 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: