|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I cannot reproduce it, both in 1.489 and 1.515.
I tried the following hierarchy:
call_1
– call_2a (blocking)
---- call_3a (blocking)
– call_2b (blocking)
---- call_3b (blocking)
Generation is OK. Execution of generated call_1 triggers all generated sub projects as well. So everything is OK.
One thing important to consider is to have enough executor on the master to be able to handle all the blocking projects.
I don't know if it's related but as you can see on the release notes for 1.10 I corrected a bug "Fixed support for Parameterized Trigger Plugin build steps (which are no longer listed as downstream projects since version 2.17)."
But at work I still have this bug...
Yet I still can't reproduce it with the example of this thread on a development environment.
Is it possible that 1.10 was not released correctly ?... Dunno, I'll release 1.11 and we'll see.