Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-18534

Jobs from same project are combined when different branches selected for each job

    Details

    • 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

            Activity

            kerrhome Shannon Kerr created issue -
            kerrhome Shannon Kerr made changes -
            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
            kerrhome Shannon Kerr made changes -
            Component/s parameterized-trigger [ 15592 ]
            Component/s parameters [ 15594 ]
            kerrhome Shannon Kerr made changes -
            Priority Major [ 3 ] Blocker [ 1 ]
            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.
            kerrhome Shannon Kerr made changes -
            Assignee huybrechts [ huybrechts ]
            kerrhome Shannon Kerr made changes -
            Priority Blocker [ 1 ] Critical [ 2 ]
            kerrhome Shannon Kerr made changes -
            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.
            kerrhome Shannon Kerr made changes -
            Priority Critical [ 2 ] Major [ 3 ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels build parameter queue build parameter queue subversion
            kerrhome Shannon Kerr made changes -
            Component/s core [ 15593 ]
            kerrhome Shannon Kerr made changes -
            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.
            Component/s parameters [ 15594 ]
            Component/s subversion [ 15485 ]
            Component/s parameterized-trigger [ 15592 ]
            kerrhome Shannon Kerr made changes -
            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
            kerrhome Shannon Kerr made changes -
            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.
            kerrhome Shannon Kerr made changes -
            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.
            danielbeck Daniel Beck made changes -
            Affects Version/s current [ 10162 ]
            Environment Ubuntu 12.04 Server, VMWare Fusion
            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.
            Component/s core [ 15593 ]
            Component/s parameters [ 15594 ]
            danielbeck Daniel Beck made changes -
            Assignee Daniel Beck [ danielbeck ]
            danielbeck Daniel Beck made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            danielbeck Daniel Beck made changes -
            Remote Link This issue links to "PR 87 (Web Link)" [ 11003 ]
            scm_issue_link SCM/JIRA link daemon made changes -
            Status In Progress [ 3 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            kerrhome Shannon Kerr made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 149841 ] JNJira + In-Review [ 206754 ]

              People

              • Assignee:
                danielbeck Daniel Beck
                Reporter:
                kerrhome Shannon Kerr
              • Votes:
                3 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: