-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Hudson v1.377, Win Server 2003 R2 x64 SP2, Join v1.9, Parametrized trigger v2.7
Hudson v1.377
Join plugin v1.9
Parametrized trigger v2.7
Job A calls job B, C, D and E via the parametrized trigger. The join in job A should start job F when all are stable. However, F started after B, C and E finished while D was still waiting for a free slave.
The parametrized trigger of B, C, D and E is called from within the join by setting the post actions.
On a side note the jobs C and D starting each another 2 jobs via parametrized triggers.
[JENKINS-9944] job triggered by join didn't wait for all downstream jobs to finish
cjo9900
added a comment - From your description/comment I think you have confused the setup.
Case 1
- tick "join trigger" start F when all downstreawm jobs have finished
- tick 'run post-build actions at join'
- tick in post-join actions "trigger parameterized build" and build jobs B, C, D and E
Case 2
- tick "join trigger" start F when all downstreawm jobs have finished
- tick 'run post-build actions at join'
- ignore the Post-Join Actions (don't tick or fill in anything)
- use "trigger parameterized build" at the bottom of the job config instead
The projects you add to the join trigger are run after all of the downstream jobs have finished, this includes the ones included in the post join parameter-trigger action.
So case 1 has no downstream jobs therefore jobs B-F are started at the same time.
In case 2 B-E are downstream jobs and F is triggered after these finish.
Cannot see any error in this case so closing.
cjo9900
added a comment - From your description/comment I think you have confused the setup.
Case 1
tick "join trigger" start F when all downstreawm jobs have finished
tick 'run post-build actions at join'
tick in post-join actions "trigger parameterized build" and build jobs B, C, D and E
Case 2
tick "join trigger" start F when all downstreawm jobs have finished
tick 'run post-build actions at join'
ignore the Post-Join Actions (don't tick or fill in anything)
use "trigger parameterized build" at the bottom of the job config instead
The projects you add to the join trigger are run after all of the downstream jobs have finished, this includes the ones included in the post join parameter-trigger action.
So case 1 has no downstream jobs therefore jobs B-F are started at the same time.
In case 2 B-E are downstream jobs and F is triggered after these finish.
Cannot see any error in this case so closing. 
This happens when I use the Join trigger in job A in the following way:
However, it seems not to occur when I change the join settings to the following: