• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: subversion-plugin
• Labels:

  • build
  • parameter
  • queue
  • subversion

[JENKINS-18534] Jobs from same project are combined when different branches selected for each job

Shannon Kerr created issue - 2013-06-27 20:02

Shannon Kerr made changes - 2013-06-28 14:08

Summary

Original: Cannot add new build to queue from same project using different parameters

New: Cannot add new build to queue from same project with different parameters

Shannon Kerr made changes - 2013-06-28 15:08

Component/s		New: parameterized-trigger [ 15592 ]
Component/s	Original: parameters [ 15594 ]

Shannon Kerr made changes - 2013-06-28 15:44

Description	Original: 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.	New: (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.
Priority	Original: Major [ 3 ]	New: Blocker [ 1 ]

Shannon Kerr made changes - 2013-06-28 15:50

Assignee

New: huybrechts [ huybrechts ]

Shannon Kerr made changes - 2013-07-01 13:03

Priority

Original: Blocker [ 1 ]

New: Critical [ 2 ]

Shannon Kerr made changes - 2013-07-03 16:13

Description

Original: (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.

New: 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.

Shannon Kerr made changes - 2013-08-13 13:18

Priority

Original: Critical [ 2 ]

New: Major [ 3 ]

Oleg Nenashev made changes - 2013-09-17 13:14

Labels

Original: build parameter queue

New: build parameter queue subversion

Shannon Kerr made changes - 2014-06-02 16:50

Component/s

New: core [ 15593 ]

Shannon Kerr made changes - 2014-06-16 20:58

Component/s		New: parameters [ 15594 ]
Component/s		New: subversion [ 15485 ]
Component/s	Original: parameterized-trigger [ 15592 ]
Assignee	Original: huybrechts [ huybrechts ]
Description	Original: 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.	New: Update: Since this appears to be an issue with the selected branch, I think this is actually a bug in the Subversion plugin. ==================== 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.

Load more newer history items