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

Use Priority from Build Parameter, but priority is ignored in queue

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Not A Defect
    • Component/s: prioritysorter-plugin
    • Labels:
      None
    • Environment:
      Jenkins version 1.614
      Priority Sorter version 3.4
    • Similar Issues:

      Description

      I'm trying to use PrioritySorter Plugin with Priority Strategy Use Priority from Build Parameter. The priority seems to be ignored though. I attached the log.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          emsa23 Magnus Sandberg added a comment -

          Note that some jobs get BLOCKED. As you are triggering the same job with different priorities they will block each other, you need to allow parallell runs of the same job for that to work.

          As you can se in the log the priority gets assigned correctly (yes?) but the prio 1 jobs is in BLOCKED state and that means it cannot be scheduled for execution.

          Show
          emsa23 Magnus Sandberg added a comment - Note that some jobs get BLOCKED. As you are triggering the same job with different priorities they will block each other, you need to allow parallell runs of the same job for that to work. As you can se in the log the priority gets assigned correctly (yes?) but the prio 1 jobs is in BLOCKED state and that means it cannot be scheduled for execution.
          Hide
          Permalink
          annafreiholtz Anna Freiholtz added a comment -

          Oh I understand, thank you for explaining! I appreciate your fast response.

          Show
          annafreiholtz Anna Freiholtz added a comment - Oh I understand, thank you for explaining! I appreciate your fast response.
          Hide
          Permalink
          annafreiholtz Anna Freiholtz added a comment -

          Just a user mistake...

          Show
          annafreiholtz Anna Freiholtz added a comment - Just a user mistake...
          Hide
          Permalink
          itspronouncedoiler John Drinkwater added a comment -

          Hello! I am running into similar issues with the "Use Priority from Build Parameter" feature. I put 5 instances of the same job into the queue with priorities ordered 4, 2, 5, 3, 1, and then turned the associated node online. I have the "Execute concurrent builds if necessary" option checked in the job's configuration, and I see no blocking in my log, yet the jobs are still being run in a FIFO manner. It seems to be completely disregarding the priority. Here is the log:

          Jun 30, 2015 11:32:21 AM FINER PrioritySorter.Queue.Items
          New Item: Id: 54458, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 4, weight: 4.0, status: WAITING
          Evaluating JobGroup [0] ...
          Checking for Job Property inclusion for [KrakenRunners]...
          JobGroup is enabled on job, with JobGroup [KrakenRunners] ...
          Job is included in JobGroup ...
          Evaluating strategies ...
          Evaluating strategy [Use Priority from Build Parameter] ...
          Strategy is applicable

          Jun 30, 2015 11:32:21 AM FINE PrioritySorter.Queue.Items
          Buildable: Id: 54458, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 4, weight: 4.0, status: BUILDABLE
          Jun 30, 2015 11:32:25 AM FINER PrioritySorter.Queue.Items
          New Item: Id: 54459, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: WAITING
          Evaluating JobGroup [0] ...
          Checking for Job Property inclusion for [KrakenRunners]...
          JobGroup is enabled on job, with JobGroup [KrakenRunners] ...
          Job is included in JobGroup ...
          Evaluating strategies ...
          Evaluating strategy [Use Priority from Build Parameter] ...
          Strategy is applicable

          Jun 30, 2015 11:32:25 AM FINE PrioritySorter.Queue.Items
          Buildable: Id: 54459, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: BUILDABLE
          Jun 30, 2015 11:32:28 AM FINER PrioritySorter.Queue.Items
          New Item: Id: 54460, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: WAITING
          Evaluating JobGroup [0] ...
          Checking for Job Property inclusion for [KrakenRunners]...
          JobGroup is enabled on job, with JobGroup [KrakenRunners] ...
          Job is included in JobGroup ...
          Evaluating strategies ...
          Evaluating strategy [Use Priority from Build Parameter] ...
          Strategy is applicable

          Jun 30, 2015 11:32:28 AM FINE PrioritySorter.Queue.Items
          Buildable: Id: 54460, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: BUILDABLE
          Jun 30, 2015 11:32:31 AM FINER PrioritySorter.Queue.Items
          New Item: Id: 54461, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: WAITING
          Evaluating JobGroup [0] ...
          Checking for Job Property inclusion for [KrakenRunners]...
          JobGroup is enabled on job, with JobGroup [KrakenRunners] ...
          Job is included in JobGroup ...
          Evaluating strategies ...
          Evaluating strategy [Use Priority from Build Parameter] ...
          Strategy is applicable

          Jun 30, 2015 11:32:31 AM FINE PrioritySorter.Queue.Items
          Buildable: Id: 54461, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: BUILDABLE
          Jun 30, 2015 11:32:33 AM FINER PrioritySorter.Queue.Items
          New Item: Id: 54462, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: WAITING
          Evaluating JobGroup [0] ...
          Checking for Job Property inclusion for [KrakenRunners]...
          JobGroup is enabled on job, with JobGroup [KrakenRunners] ...
          Job is included in JobGroup ...
          Evaluating strategies ...
          Evaluating strategy [Use Priority from Build Parameter] ...
          Strategy is applicable

          Jun 30, 2015 11:32:33 AM FINE PrioritySorter.Queue.Items
          Buildable: Id: 54462, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: BUILDABLE
          Jun 30, 2015 11:32:37 AM FINE PrioritySorter.Queue.Items
          Starting: Id: 54458, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 4, weight: 4.0, status: BUILDABLE
          Jun 30, 2015 11:32:37 AM FINE PrioritySorter.Queue.Items
          Starting: Id: 54459, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: BUILDABLE
          Jun 30, 2015 11:32:38 AM FINE PrioritySorter.Queue.Items
          Starting: Id: 54460, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: BUILDABLE
          Jun 30, 2015 11:32:39 AM FINE PrioritySorter.Queue.Items
          Starting: Id: 54461, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: BUILDABLE
          Jun 30, 2015 11:32:40 AM FINE PrioritySorter.Queue.Items
          Starting: Id: 54462, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: BUILDABLE

          Show
          itspronouncedoiler John Drinkwater added a comment - Hello! I am running into similar issues with the "Use Priority from Build Parameter" feature. I put 5 instances of the same job into the queue with priorities ordered 4, 2, 5, 3, 1, and then turned the associated node online. I have the "Execute concurrent builds if necessary" option checked in the job's configuration, and I see no blocking in my log, yet the jobs are still being run in a FIFO manner. It seems to be completely disregarding the priority. Here is the log: Jun 30, 2015 11:32:21 AM FINER PrioritySorter.Queue.Items New Item: Id: 54458, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 4, weight: 4.0, status: WAITING Evaluating JobGroup [0] ... Checking for Job Property inclusion for [KrakenRunners] ... JobGroup is enabled on job, with JobGroup [KrakenRunners] ... Job is included in JobGroup ... Evaluating strategies ... Evaluating strategy [Use Priority from Build Parameter] ... Strategy is applicable Jun 30, 2015 11:32:21 AM FINE PrioritySorter.Queue.Items Buildable: Id: 54458, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 4, weight: 4.0, status: BUILDABLE Jun 30, 2015 11:32:25 AM FINER PrioritySorter.Queue.Items New Item: Id: 54459, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: WAITING Evaluating JobGroup [0] ... Checking for Job Property inclusion for [KrakenRunners] ... JobGroup is enabled on job, with JobGroup [KrakenRunners] ... Job is included in JobGroup ... Evaluating strategies ... Evaluating strategy [Use Priority from Build Parameter] ... Strategy is applicable Jun 30, 2015 11:32:25 AM FINE PrioritySorter.Queue.Items Buildable: Id: 54459, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: BUILDABLE Jun 30, 2015 11:32:28 AM FINER PrioritySorter.Queue.Items New Item: Id: 54460, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: WAITING Evaluating JobGroup [0] ... Checking for Job Property inclusion for [KrakenRunners] ... JobGroup is enabled on job, with JobGroup [KrakenRunners] ... Job is included in JobGroup ... Evaluating strategies ... Evaluating strategy [Use Priority from Build Parameter] ... Strategy is applicable Jun 30, 2015 11:32:28 AM FINE PrioritySorter.Queue.Items Buildable: Id: 54460, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: BUILDABLE Jun 30, 2015 11:32:31 AM FINER PrioritySorter.Queue.Items New Item: Id: 54461, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: WAITING Evaluating JobGroup [0] ... Checking for Job Property inclusion for [KrakenRunners] ... JobGroup is enabled on job, with JobGroup [KrakenRunners] ... Job is included in JobGroup ... Evaluating strategies ... Evaluating strategy [Use Priority from Build Parameter] ... Strategy is applicable Jun 30, 2015 11:32:31 AM FINE PrioritySorter.Queue.Items Buildable: Id: 54461, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: BUILDABLE Jun 30, 2015 11:32:33 AM FINER PrioritySorter.Queue.Items New Item: Id: 54462, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: WAITING Evaluating JobGroup [0] ... Checking for Job Property inclusion for [KrakenRunners] ... JobGroup is enabled on job, with JobGroup [KrakenRunners] ... Job is included in JobGroup ... Evaluating strategies ... Evaluating strategy [Use Priority from Build Parameter] ... Strategy is applicable Jun 30, 2015 11:32:33 AM FINE PrioritySorter.Queue.Items Buildable: Id: 54462, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: BUILDABLE Jun 30, 2015 11:32:37 AM FINE PrioritySorter.Queue.Items Starting: Id: 54458, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 4, weight: 4.0, status: BUILDABLE Jun 30, 2015 11:32:37 AM FINE PrioritySorter.Queue.Items Starting: Id: 54459, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: BUILDABLE Jun 30, 2015 11:32:38 AM FINE PrioritySorter.Queue.Items Starting: Id: 54460, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: BUILDABLE Jun 30, 2015 11:32:39 AM FINE PrioritySorter.Queue.Items Starting: Id: 54461, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: BUILDABLE Jun 30, 2015 11:32:40 AM FINE PrioritySorter.Queue.Items Starting: Id: 54462, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: BUILDABLE
          Hide
          Permalink
          emsa23 Magnus Sandberg added a comment -

          This item is closed please open a new issue if you have problems.

          In the meanwhile make sure you also log from "PrioritySorter.Queue.Sorter" to see that the sorting actually happens.

          As soon as a Job as been given a priority the reason does not matter, sorting is happening in the same way.

          Show
          emsa23 Magnus Sandberg added a comment - This item is closed please open a new issue if you have problems. In the meanwhile make sure you also log from "PrioritySorter.Queue.Sorter" to see that the sorting actually happens. As soon as a Job as been given a priority the reason does not matter, sorting is happening in the same way.

            People

            Assignee:
            emsa23 Magnus Sandberg
            Reporter:
            annafreiholtz Anna Freiholtz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: