|
||||||||
|
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/groups/opt_out.
This was unexpected to us as well. Additionally, few days ago the job somehow switched back to "trunk" few minutes after it was run manually to test a branch. Later, both "chains" of builds mixed together, i.e., triggered a single downstream build from two different upstream builds. Upstream builds had different parameters which are passed to downstream jobs, therefore there had to be 2 downstream builds to test both branch and trunk.
Possible workaround - remove SCM polling from your "starter job" and add 2 new jobs - one for polling, another for running it manually. Then, use "Trigger parameterized build on other projects" to run your current "starter job".