|
||||||||
|
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/groups/opt_out.
The sorting doesn't happen immediately when a jobs are added, it just happens at intervals (this is how Jenkins works and is nothing that is controlled by the plugin) this means that jobs might get started when added if there's room for them.
If the slaves are all busy you should see the queue getting sorted, I have not tested with 1.531.1 but I have not seen any issues like this in any other version I have tested.
If you look under "Troubleshooting" on the wiki page it describes how to turn on some extra logging to verify what priorities gets assigned to jobs, you can also see when Jobs jumps between states in the queue and when they get removed fro the queue (started).
Could you please turn on this logging and provide logs in this issue that showcases the bad behaviour, this will give me a better starting point to find out what is going on.