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

8 views
Skip to first unread message

ntomeky@gmail.com (JIRA)

unread,
Apr 24, 2020, 4:08:03 AM4/24/20
to jenkinsc...@googlegroups.com
Tomasz Koźlak created an issue
 
Jenkins / Bug JENKINS-62041
PrioritySorter doesn't work as expected. High Prio jobs last in queue
Issue Type: Bug Bug
Assignee: Unassigned
Attachments: job_priority.PNG
Components: prioritysorter-plugin
Created: 2020-04-24 08:07
Priority: Major Major
Reporter: Tomasz Koźlak

Hi,

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

Plugin version 3.6.0, Pipeline version 2.6

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.

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

ntomeky@gmail.com (JIRA)

unread,
Apr 24, 2020, 5:04:03 AM4/24/20
to jenkinsc...@googlegroups.com
Tomasz Koźlak updated an issue
Change By: Tomasz Koźlak
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|https://jenkins.io/]

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.

 

ntomeky@gmail.com (JIRA)

unread,
Apr 24, 2020, 5:59:05 AM4/24/20
to jenkinsc...@googlegroups.com
Tomasz Koźlak commented on Bug JENKINS-62041
 
Re: PrioritySorter doesn't work as expected. High Prio jobs last in queue

Also tried with "Jobs included in groups" but result is the same -> FIFO.

ntomeky@gmail.com (JIRA)

unread,
Apr 24, 2020, 6:00:05 AM4/24/20
to jenkinsc...@googlegroups.com

ntomeky@gmail.com (JIRA)

unread,
Apr 29, 2020, 2:21:03 AM4/29/20
to jenkinsc...@googlegroups.com
 
Re: PrioritySorter doesn't work as expected. High Prio jobs last in queue

I solved the problem by downgrading Pipepilne plugin from 2.6 to 2.5.

Reply all
Reply to author
Forward
0 new messages