Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: subversion-plugin
-
Labels:
-
Similar Issues:
Description
Different values selected for 'List Subversion Tags' parameters are not considered in determining parameter equality.
ListSubversionTagsParameterValue needs to implement hashCode() and equals() properly.
Attachments
Issue Links
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Summary | Cannot add new build to queue from same project using different parameters | Cannot add new build to queue from same project with different parameters |
Component/s | parameterized-trigger [ 15592 ] | |
Component/s | parameters [ 15594 ] |
Description |
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. |
(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 | Major [ 3 ] | Blocker [ 1 ] |
Assignee | huybrechts [ huybrechts ] |
Priority | Blocker [ 1 ] | Critical [ 2 ] |
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. |
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 | Critical [ 2 ] | Major [ 3 ] |
Labels | build parameter queue | build parameter queue subversion |
Component/s | core [ 15593 ] |
Component/s | parameters [ 15594 ] | |
Component/s | subversion [ 15485 ] | |
Component/s | parameterized-trigger [ 15592 ] | |
Assignee | huybrechts [ huybrechts ] | |
Description |
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. |
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. |
Summary | Cannot add new build to queue from same project with different parameters | Jobs from same project are combined when different branches selected for each job |
Description |
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. |
Update: Since this appears to be an issue with the selected branch, I think this is actually a bug in the Subversion plugin. ==================== (rewriting the description) When two different jobs from the same project are started by the same or different users and the only difference, besides possibly the user, is the branch/tag name, the jobs are combined in the queue and executed as a single job. This makes no sense though since user Jim could have selected branch "bugfix" and user Suzy could have selected branch "feature_1". Since Suzy was second, we end up only building "feature_1" and slapping both Jim and Suzy's names on the build. ======================= (original description) 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. |
Description |
Update: Since this appears to be an issue with the selected branch, I think this is actually a bug in the Subversion plugin. ==================== (rewriting the description) When two different jobs from the same project are started by the same or different users and the only difference, besides possibly the user, is the branch/tag name, the jobs are combined in the queue and executed as a single job. This makes no sense though since user Jim could have selected branch "bugfix" and user Suzy could have selected branch "feature_1". Since Suzy was second, we end up only building "feature_1" and slapping both Jim and Suzy's names on the build. ======================= (original description) 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. |
Update: Since this appears to be an issue with the selected branch, I think this is actually a bug in the Subversion plugin. ==================== (rewriting the description) When two different jobs from the same project are started by the same or different users and the only difference, besides possibly the user, is the branch/tag name, the jobs are combined in the queue and executed as a single job. This makes no sense though since user Jim could have selected branch "bugfix" and user Suzy could have selected branch "feature_1". Since Suzy was second, we end up only building "feature_1" and slapping both Jim and Suzy's names on the build. Other build parameters prevent the jobs from being combined in the queue, but a branch/tag selected from the SVN plugin's drop down list does not. ======================= (original description) 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. |
Component/s | core [ 15593 ] | |
Component/s | parameters [ 15594 ] | |
Affects Version/s | current [ 10162 ] | |
Description |
Update: Since this appears to be an issue with the selected branch, I think this is actually a bug in the Subversion plugin. ==================== (rewriting the description) When two different jobs from the same project are started by the same or different users and the only difference, besides possibly the user, is the branch/tag name, the jobs are combined in the queue and executed as a single job. This makes no sense though since user Jim could have selected branch "bugfix" and user Suzy could have selected branch "feature_1". Since Suzy was second, we end up only building "feature_1" and slapping both Jim and Suzy's names on the build. Other build parameters prevent the jobs from being combined in the queue, but a branch/tag selected from the SVN plugin's drop down list does not. ======================= (original description) 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. |
Different values selected for 'List Subversion Tags' parameters are not considered in determining parameter equality. ListSubversionTagsParameterValue needs to implement hashCode() and equals() properly. |
Environment | Ubuntu 12.04 Server, VMWare Fusion |
Assignee | Daniel Beck [ danielbeck ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Remote Link | This issue links to "PR 87 (Web Link)" [ 11003 ] |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Workflow | JNJira [ 149841 ] | JNJira + In-Review [ 206754 ] |
I just now tested this back to Jenkins 1.518 and it has the same behavior. Again, I thought I had verified this works previously (2 builds of the same project in the queue at the same time), but now I am not 100% confident. I'll need to create a new instance of Jenkins to test this out and try going back to a much older (for me) release.