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

Ability to specify the order of post build actions

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • All

      Currently there is no way to specify the order in which the post build actions should get executed. It will be great to have ability to specify the order on the job configuration page (Just like how we can drag and drop the build steps in ay order that we want)

      The project configuration should then persist this order and execute the post build actions (such as JUnit result processing. PMD, FindBugs processing etc etc ) in that order.

      We want the trend graphs (for PMD, FindBugs, JUnit etc.) to be displayed in the order of their importance for the project. Currently it appears that the graphs are getting displayed in the order of their plugin names.

          [JENKINS-7408] Ability to specify the order of post build actions

          rodym added a comment - - edited

          We have a similar issue: we use the Sonar plugin to publish stuff to the Sonar instance and I want to have the PMD, Checkstyle publishers to be run AFTER the Sonar Publisher is ready.

          rodym added a comment - - edited We have a similar issue: we use the Sonar plugin to publish stuff to the Sonar instance and I want to have the PMD, Checkstyle publishers to be run AFTER the Sonar Publisher is ready.

          Victor Garcia Perez added a comment -

          The same for us.
          The plugin that allow you to execute Groovy code in the postbuild actions (Groovy postbuild plugin) doesn't have any sense if the order of these actions is undetermined.

          Victor Garcia Perez added a comment - The same for us. The plugin that allow you to execute Groovy code in the postbuild actions (Groovy postbuild plugin) doesn't have any sense if the order of these actions is undetermined.

          Daniel Tkatch added a comment -

          Same here. Some actions done with Groovy Postbuild plugin are overwritten by JUnit publisher, cause it runs later.

          Daniel Tkatch added a comment - Same here. Some actions done with Groovy Postbuild plugin are overwritten by JUnit publisher, cause it runs later.

          bap added a comment -

          This plugin enables you to execute many post-build tasks in an order of your choosing:
          https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin

          It may, or may not affect the order in which reports are displayed

          bap added a comment - This plugin enables you to execute many post-build tasks in an order of your choosing: https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin It may, or may not affect the order in which reports are displayed

          bap added a comment -

          I can confirm that the order that the graphs are displayed can be changed by using the Flexible Publish Plugin

          I have just moved my Test Result Trend to the top of the page (above my Open Tasks Trend)

          bap added a comment - I can confirm that the order that the graphs are displayed can be changed by using the Flexible Publish Plugin I have just moved my Test Result Trend to the top of the page (above my Open Tasks Trend)

          Henri Gomez added a comment -

          +100

          It became mandatory for some of our jobs also.

          Henri Gomez added a comment - +100 It became mandatory for some of our jobs also.

          Arnaud Héritier added a comment -

          Was fixed in 1.463. See : https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-dev/UQLvxQclyb4

          Arnaud Héritier added a comment - Was fixed in 1.463. See : https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-dev/UQLvxQclyb4

          Henri Gomez added a comment -

          I was using 1.447 (LTS) and updated some instances to 1.465 and see it was fixed.
          Sorry for the noise

          Henri Gomez added a comment - I was using 1.447 (LTS) and updated some instances to 1.465 and see it was fixed. Sorry for the noise

            kohsuke Kohsuke Kawaguchi
            zankya zankya
            Votes:
            19 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: