-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Linux
I have several jobs which use this plugin. They are configured to run another job upon success or failure of the parent job. The parent job runs a shell script build step. If the job succeeds the downstream job is triggered correctly. If the job fails, though, no downstream job is triggered and nothing in the console log indicates what the problem is.
- is duplicated by
-
JENKINS-8985 trigger parameterized builds only triggers the first instance of a project
-
- Resolved
-
- is related to
-
JENKINS-7377 Job is not invoked if there are no parameters specified
-
- Resolved
-
-
JENKINS-8488 Need a trigger for Unstable and Failed but not Stable
-
- Resolved
-
I just did some more experimenting and figured out more specifically what the problem is.
If you create two triggers for the same job, one for the pass case and one for the fail case, only the first one will ever work. For example if we set up triggers like this:
Build A passes
Run Build B with param="Yay"
Build A fails
Run Build B with param="Oh no!"
Only the passing case will ever work. If Job A fails, nothing will happen. If we happen to swap the two, and define the failure case first, then that will always work and the pass case will never trigger.
Multiple passing triggers of DIFFERENT jobs always work.