|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
It's still not clear to me whether there's a real problem here.
Could you provide exhaustive steps to reproduce this issue in a minimal test case, i.e. leave out actual Git repos if possible, use only e.g. parameterized builds and and parameterized trigger; but explain that in detail. Be specific as to what need to be configured, and how. For example, don't just imply that one job somehow starts others, write instead something like Add a 'Trigger parameterized build on other projects' post-build action, have it trigger the project 'foo' with 'Current build parameters' selected from the 'Add Parameters' dropdown, then save the configuration.