I have a parent job, which triggers child1 and child2 Jobs through this plugin. I have set the "Fail this build step if the triggered build is worse or equal to: UNSTABLE" on the first child.

      When child1 fails with status UNSTABLE, I would expect the parent to also stop, but it still triggers the child2 job.

          [JENKINS-14518] Failed first job still triggers second job

          cjo9900 added a comment -

          I would say that this is the intended behaviour, as the plugin will try and build all triggers regardless of the results of each trigger. This is required in some cases where all of the child projects need to run but have different sets of parameters.

          If you have the second child job not run if the first fails add a separate second trigger build step for that project which will not run as the first build step will have caused the build to fail.

          trigger buildstep 1
          child 1
          parameters
          fail step if triggered project fails.
          trigger buildstep 2
          child 2
          other options

          cjo9900 added a comment - I would say that this is the intended behaviour, as the plugin will try and build all triggers regardless of the results of each trigger. This is required in some cases where all of the child projects need to run but have different sets of parameters. If you have the second child job not run if the first fails add a separate second trigger build step for that project which will not run as the first build step will have caused the build to fail. trigger buildstep 1 child 1 parameters fail step if triggered project fails. trigger buildstep 2 child 2 other options

          cjo9900 added a comment -

          Intended behaviour of the build step.

          cjo9900 added a comment - Intended behaviour of the build step.

          Marc Günther added a comment -

          Thanks for that idea, that never occurred to me.

          Maybe a good idea to add this to the help somehow. I found it confusing that the "fail this build step" option still triggered the next build. But it was of course still the same build step, so it makes kind of sense when you think about it.

          Marc Günther added a comment - Thanks for that idea, that never occurred to me. Maybe a good idea to add this to the help somehow. I found it confusing that the "fail this build step" option still triggered the next build. But it was of course still the same build step, so it makes kind of sense when you think about it.

            cjo9900 cjo9900
            marc_guenther Marc Günther
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: