On Wed, Feb 13, 2013 at 4:48 AM, Mandeville, Rob <[email protected]>wrote:
> I’m using the priority sorter plugin, and getting confused. The page > for the plugin at > https://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin says > that “A priority of 50 comes before a priority of 100”, so a lower priority > number is a higher priority. > I think the plugin author meant this: It "comes before" in the queue. Look at the queue literally -- I mean literally visually. The top of the list is the lowest priority. The bottom of that list is the highest priority, those jobs are going to run next. > When I look at the source, PrioritySorterQueueSorter.java runs the compare > in reverse order, complete with a comment stating “Note that we sort these > backwards because we want to return higher-numbered items first”. When I > tried launching jobs of different priorities from the Web UI, they ran in > launch order, apparently ignoring the priority sorter plugin. When I ran a > build that launches sub-builds of different priorities via “trigger > parameterized builds on other projects”, they got launched but required a > label that was completely in uses, so they got queued. The four jobs with > priority 100 launched before the one with priority 90.**** > > ** ** > > Am I correct in assuming that, if two jobs are waiting on an executor on a > node or label, the one with the higher priority number will get in first? > This was already answered in a previous post. Note, I did post an enhancement request to the plugin author to have the plugin also look at the jobs in the execution queue. > And if that is the case, should somebody edit the wiki for the plugin? > Post a bug on the plugin site. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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/groups/opt_out.
