It would be really useful, if the plugin would support some kind of way to asynchronously wait for the started jobs to finish, i.e. to
(plugin) kick-off the jobs (but don't wait until they're done)
continue with current job
(plugin) wait for previously started jobs to finish to get status and build numbers
continue with current job
This would increase performance in cases, where the build steps executed by the job using the plugin cannot be moved to a different job for parallel execution.
It would be really useful, if the plugin would support some kind of way to asynchronously wait for the started jobs to finish, i.e. to
# (plugin) kick-off the jobs (but don't wait until they're done) # continue with current job # (plugin) wait for previously started jobs to finish to get status and build numbers # continue with current job
This would increase performance in cases, where the build steps executed by the job using the plugin cannot be moved to a different job for parallel execution or in case multiple jobs need to be triggered with different parameter sets.
I think I am seeing the same issue, manifested differently. My upstream job triggers several downstream jobs via trigger-builds, which in turn trigger other jobs (all blocking). From what I can see all jobs get trigerred but console log sits and waits on the first job to complete before displaying the rest of them.