Hi Chris,
thanks for your reply.
I have modified the dispatcher that it isn't waiting anymore. The
dispatcher gives an instant feedback build history if a job was started
successfully and the downstream job notifies by mail if success or fail.
That's good emough for me. Minumum effort with max
Looks like you really want the parameterized-trigger with more conditions,
this is currently a pull request
which make the parameterized-trigger have all of the same conditions as the
conditional build step plugin.
If you want to try this it is request
https://github.com/jenkinsci/parameterized
Never mind,
seems that I have been mixing my memories up. Seems that it not is possible
to keep dispatcher running and wait for the child job in multiple
instances. Even if I actually still am convinced that it did work.
Removing the Block option in the conditional build trigger solves it so far
Hi folks,
I am facing some funny (well...not) situation.
My current project involves also some serious parallelization.
There is one main job doing some unspectacular operations like string split
and compare in order to decide via conditional build steps which job has to
be launched. So I call
