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

Trigger downstream builds in any case

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      The current implementation of the parameterized trigger plugin allows to trigger downstream builds by these build results:

      • Stable
      • Unstable
      • Stable or unstable but not failed
      • Failed

      I'd like to suggest an additional option:

      • Stable, unstable, or failed (trigger always)

      Use case: Sometimes you would like to trigger a downstream build in any case, because the downstream case does some clean-up after an upstream project and you would like to do this housekeeping regardless of the outcome of the upstream project.

      A patch is attached (patch_ResultCondition.txt).

      Anybody out there who would like to review it?

        Attachments

          Activity

          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in hudson
          User: : mindless
          Path:
          trunk/hudson/plugins/parameterized-trigger/src/main/java/hudson/plugins/parameterizedtrigger/ResultCondition.java
          http://jenkins-ci.org/commit/33358
          Log:
          [parameterized-trigger] [FIXED JENKINS-6656] add "trigger always" option,
          as suggested by swiest

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : mindless Path: trunk/hudson/plugins/parameterized-trigger/src/main/java/hudson/plugins/parameterizedtrigger/ResultCondition.java http://jenkins-ci.org/commit/33358 Log: [parameterized-trigger] [FIXED JENKINS-6656] add "trigger always" option, as suggested by swiest
          Hide
          liyatikal liyatikal added a comment -

          I'm using the latest Hudson 1.379 running on Ubuntu server.
          I have a nightly jobs chain that suppose to run one after another no matter if the previous one was successful/unstable or failed.
          The trigger for every job is defined as "Complete (always trigger)", but only when the build was successful the next job is running.

          Can I provide any configuration details that can help?..

          Show
          liyatikal liyatikal added a comment - I'm using the latest Hudson 1.379 running on Ubuntu server. I have a nightly jobs chain that suppose to run one after another no matter if the previous one was successful/unstable or failed. The trigger for every job is defined as "Complete (always trigger)", but only when the build was successful the next job is running. Can I provide any configuration details that can help?..
          Hide
          mindless Alan Harder added a comment -

          can you attach config.xml for the job where this isn't working?
          if you make a new job that simply has a shell build step doing "exit 1" (so it will fail), do you also see this trigger not working?

          Show
          mindless Alan Harder added a comment - can you attach config.xml for the job where this isn't working? if you make a new job that simply has a shell build step doing "exit 1" (so it will fail), do you also see this trigger not working?
          Hide
          mindless Alan Harder added a comment -

          also post the last bit of the console output from your job.. I got this:

          + exit 1
          Triggering a new build of foo #21
          Finished: FAILURE
          

          ..and it did trigger the downstream job as it says..

          Show
          mindless Alan Harder added a comment - also post the last bit of the console output from your job.. I got this: + exit 1 Triggering a new build of foo #21 Finished: FAILURE ..and it did trigger the downstream job as it says..
          Hide
          liyatikal liyatikal added a comment -

          The triggering didn't work because of another bug http://issues.jenkins-ci.org/browse/JENKINS-7671

          Show
          liyatikal liyatikal added a comment - The triggering didn't work because of another bug http://issues.jenkins-ci.org/browse/JENKINS-7671

            People

            • Assignee:
              mindless Alan Harder
              Reporter:
              swiest Simon Wiest
            • Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: