|
||||||||
|
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.
It is the same argument with FIFO. If there is a lots of jobs then the newer ones will have to wait a lot of time to be executed (I agree that with stack approach it may happen that some jobs get starved because the executors can't absorb all of what is added to the queue, but in the real world scenario they will get executed eventually when the queue is processed and not much is added (e.g. during the night or lunch break).
I think that perishable goods are not a good analogy to the jenkins jobs i.e. the jobs doesn't spoil, and the consumer doesn't loose interest in them (they have to be consumed at some point anyway).
Acutally the QueueSorter is too late in the process it doesn't see the whole waitingList, not sure about QueueTaskDispatcher though.