Hi Magnus, Hi Markus,

I am facing similar problems like described above. Starting the same job with different priorities via GUI or via POSTing URL results in a queue which is processed in the same order I added them with no respect to any priorities applied.

Here is the log:

Jun 11, 2014 2:32:19 PM FINER PrioritySorter.Queue.Items

New Item: Id: 41, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: WAITING
Evaluating JobGroup [0] ...
Evaluating View [All] ...
Not using filter ...
Evaluating strategies ...
Evaluating strategy [Use Priority from Build Parameter] ...
Strategy is applicable

Jun 11, 2014 2:32:19 PM FINE PrioritySorter.Queue.Items

Buildable: Id: 41, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: BUILDABLE

Jun 11, 2014 2:32:19 PM FINE PrioritySorter.Queue.Items

Starting: Id: 41, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: BUILDABLE

Jun 11, 2014 2:32:26 PM FINER PrioritySorter.Queue.Items

New Item: Id: 42, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: WAITING
Evaluating JobGroup [0] ...
Evaluating View [All] ...
Not using filter ...
Evaluating strategies ...
Evaluating strategy [Use Priority from Build Parameter] ...
Strategy is applicable

Jun 11, 2014 2:32:26 PM FINE PrioritySorter.Queue.Items

Blocking: Id: 42, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: BLOCKED

Jun 11, 2014 2:32:34 PM FINER PrioritySorter.Queue.Items

New Item: Id: 43, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: WAITING
Evaluating JobGroup [0] ...
Evaluating View [All] ...
Not using filter ...
Evaluating strategies ...
Evaluating strategy [Use Priority from Build Parameter] ...
Strategy is applicable

Jun 11, 2014 2:32:34 PM FINE PrioritySorter.Queue.Items

Blocking: Id: 43, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: BLOCKED

Jun 11, 2014 2:32:39 PM FINE PrioritySorter.Queue.Items

Buildable: Id: 42, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: BUILDABLE

Jun 11, 2014 2:32:39 PM FINE PrioritySorter.Queue.Items

Starting: Id: 42, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: BUILDABLE

Jun 11, 2014 2:32:51 PM FINER PrioritySorter.Queue.Items

New Item: Id: 44, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: WAITING
Evaluating JobGroup [0] ...
Evaluating View [All] ...
Not using filter ...
Evaluating strategies ...
Evaluating strategy [Use Priority from Build Parameter] ...
Strategy is applicable

Jun 11, 2014 2:32:51 PM FINE PrioritySorter.Queue.Items

Blocking: Id: 44, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: BLOCKED

Jun 11, 2014 2:32:59 PM FINE PrioritySorter.Queue.Items

Buildable: Id: 43, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: BUILDABLE

Jun 11, 2014 2:32:59 PM FINE PrioritySorter.Queue.Items

Starting: Id: 43, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: BUILDABLE

Jun 11, 2014 2:33:29 PM FINE PrioritySorter.Queue.Items

Buildable: Id: 44, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: BUILDABLE

Jun 11, 2014 2:33:29 PM FINE PrioritySorter.Queue.Items

Starting: Id: 44, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: BUILDABLE

With best regards,

Marcus

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/d/optout.

Reply via email to