![]() |
|
|
|
|
Change By:
|
Shannon Kerr
(03/Jul/13 4:13 PM)
|
|
Description:
|
(Changed to Blocker as this bug is preventing us from rolling out Jenkins to production right now, but
I
could completely change our implementation and reduce this to Critical or Major I suppose, but that would be quite a bit of work)
I
start a parameterized build from project A via the build button.
A second parameterized build from the same project was then started via the build button, but with different parameter values.
Instead of having two jobs in the queue, the second job is not added and instead takes over the first job in the queue.
If the jobs were started by different users, both users names show up as the "Started by" users.
Only the second user's parameters are used and retained. The first user's job is just lost.
I'm going to see if this ever worked, but I'm pretty sure it did. I'm still pretty new to Jenkins, but I thought I had tested this out before and had seen two instances of the same job sitting in the queue.
|
|
|
|
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.
