[JENKINS-62041] PrioritySorter doesn't work as expected. High Prio jobs last in queue

Hi,

I'm not sure if Piority Sorter works as it should.

Plugin version 3.6.0, Pipeline version 2.6, Jenkins ver. 2.190.1

Absolute strategy.

Example: I have got 2 jobs in seperate folders, jobs use the same node to run. Job included in Folder1 is set with HIGH Priority (equal 1), job included in Folder2 is set with LOW Priority (equal 5). For testing purpose I run 10 times LOW Prio job and then 2 runs HIGH Prio Job. I expect that these 2 high prio runs will start before all other jobs in queue. But it's not happening. You can see screenshot from Build Queue plugin. All jobs are waiting for available executor. Two last rows are HIGH Prio jobs. I would expect that these two will be move on top of queue.

 

---
Originally reported by tomkoz, imported from: PrioritySorter doesn't work as expected. High Prio jobs last in queue

• status: Open
  
• priority: Critical
  
• component(s): prioritysorter-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 3
  
• imported: 20251211-071809
  

Raw content of original issue

Hi,


I'm not sure if Piority Sorter works as it should.


Plugin version 3.6.0, Pipeline version 2.6, Jenkins ver. 2.190.1


Absolute strategy.


Example: I have got 2 jobs in seperate folders, jobs use the same node to run. Job included in Folder1 is set with HIGH Priority (equal 1), job included in Folder2 is set with LOW Priority (equal 5). For testing purpose I run 10 times LOW Prio job and then 2 runs HIGH Prio Job. I expect that these 2 high prio runs will start before all other jobs in queue. But it's not happening. You can see screenshot from Build Queue plugin. All jobs are waiting for available executor. Two last rows are HIGH Prio jobs. I would expect that these two will be move on top of queue.


 

1 attachment

- [job_priority.PNG](https://issues.jenkins.io/secure/attachment/51059/job_priority.PNG)
> 

Reproduce the case in the priority-sorter-plugin using the Absolute strategy: queue ten LOW-priority runs followed by two HIGH-priority runs on jobs sharing one node. Compare the Build Queue view and start order with the expected behavior that the HIGH-priority runs move ahead of the queued LOW-priority runs; use Jenkins 2.190.1, Pipeline 2.6, and plugin 3.6.0 as the reported versions.

Written by the indexing model from the issue text.