![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Magnus Sandberg
|
|
Components:
|
prioritysorter |
|
Created:
|
08/Sep/14 5:52 AM
|
|
Description:
|
We are seeing problems with ignored priorities in the plugin, so I decided to make the simplest test I could think of:
Start a build on one machine with only one executor that runs for half a minute.
While it is building, start 2 builds of jobs with varying absolute priorities set, 1 and 2.
Watch in which order the other builds are run.
Everytime I do this test, the builds are executed in FIFO order, with no concern of priority.
If I repeat this test with the older priority mechanism of the plugin, it works like it should.
|
|
Environment:
|
Jenkins 1.520, priority sorter 2.8
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Tomas Westling
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
