|
||||||||
|
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 just attempted to start multiple instance of the same build, all with unique parameters and it was a mess.
Here is what I see:
1. Sometimes it created a new unique job
2. Sometimes it "merged" with the next job in the queue, replacing the parameters
In my testing I used the following parameters:
1. Branch (drop down list box of the available branches)
2. Build type (choice between -D and -R)
3. Check box for Test build (is this a test build?)
I tried different combinations of each of these and could not get consistent behavior.
We're just getting ready to roll out Jenkins and this kind of bug is really throwing off the plan to roll out. Hope to see it fixed soon, or someone can educate me on what I'm not doing right.
Thanks!