>From the main page, I have selected priority strategy to be "Use priority from Build Parameter. And I am using "BuildPriority" as the build parameter name. I have same parameter in the job by extended choice parameter. I submit the build with BuildPriority=4,3,1 respectively.
I am expecting builds to be run in following orders: 4 (since its the 1st job submitted,1 and 3). But, builds run according to FIFO ie., 4,3,1. On Monday, 3 March 2014 21:31:42 UTC+5:30, Baptiste Mathus wrote: > > This is indeed exactly how we use the priority sorter. Using a parameter. > So maybe double check what you did or explain in details here how you > proceed. > Cheers > Le 3 mars 2014 14:07, "Jayaprakash D B" <[email protected] <javascript:>> > a écrit : > >> Hi All, >> >> I am using priority sorter plugin for a project. I want the priority >> values to be set as part of parametrized value. If I am not wrong, it's not >> supported directly. >> >> Under Job Priorities page, I tried setting the "Use priority from Build >> parameter option". For "Build Parameter Name" I set the variable to be >> BuildPriority which I get as a parameterized value while submitting the >> build. But I couldn't use it effectively. >> >> Am I missing something here? >> >> -- >> 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] <javascript:>. >> 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
