Yep . . . <shrug> . . . All I know is if I want to temporally boost the priority of a job without losing what the original value "was" . . . I add a zero on the end, save and it jumps to the front of the queue. At a later time I can come back and remove the zero to return it to its normally assigned priority.
Your mileage may vary. Frank -----Original Message----- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Adam Mercer Sent: Tuesday, February 12, 2013 1:32 PM To: jenkinsci-users@googlegroups.com Subject: Re: Priority Sorter Plugin On Tue, Feb 12, 2013 at 3:26 PM, Merrow, Frank <fmer...@qti.qualcomm.com> wrote: > The priority for this job. Priorities are used when all executors are > busy to decide which job in the build queue to run next. A job with > higher priority is ran before jobs with lower priorities. > > So the job you want to run first should be 200 . . . not 50. But that contradicts what the documentation on the plugin webpage says: "The default priority is 100. Jobs will be ordered in ascending order. A priority of 50 comes before a priority of 100." Cheers Adam -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
