[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand commented on JENKINS-22294 Priority is not used in the scheduling Logging was essential, I had PrioritySorter.Queue.Items and PrioritySorter.Queue.sorter logging with "ALL" lOGS showed that priority sorter was applying priority based on first JobGroup (id=0) - this one was NOT configured to use BuildParameterStrategy - only second JobGroup(id=1) was, and didn't match the view. So By setting the JobGroups and the vieWs and the jobs all in sync solved the issue. Without the finest level of logs it was really hard to understand what happened. 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Magnus Sandberg commented on JENKINS-22294 Priority is not used in the scheduling Sorry if the way to configure this is not clear. Please suggest changes to the wiki. In any case increasing the logging will help in most cases as the detailed log will tell you what Strategies are tried and what one is finally matched and used. 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Daniel Beck commented on JENKINS-22294 Priority is not used in the scheduling How did you solve it? 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand closed JENKINS-22294 as Fixed Priority is not used in the scheduling Nicolas De Loof (CloudBees Support) helped me to figure out the correct Configuration settings. It was not that obvious how to configure JobGroup with BuildParameterStrategy. Change By: Markus Strand (18/Sep/14 10:58 PM) Status: Open Closed Resolution: Fixed 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Magnus Sandberg commented on JENKINS-22294 Priority is not used in the scheduling Looks like the priority-parameter is not used. Try to turn on FINER logging for "PrioritySorter.Queue.Items" this should tell how the priority is assigned. 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand commented on JENKINS-22294 Priority is not used in the scheduling Interesting. the Problem is not with static priorities, but with the priority parameter. I start the builds in "reverse priority order". The build queue in the job page shows them sorted in priority order: pending #27 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=6 pending #26 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=4 pending #25 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=3 pending #24 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=2 pending #23 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=1 In progress Console Output #22 Aug 25, 2014 7:56:28 AM cancel The queue is all with the same priority: Aug 25, 2014 7:57:27 AM FINER PrioritySorter.Queue.Sorter Queue: -- Item Id Job Name Priority Weight -- 5921 testPriorityN 5 5.0 5922 testPriorityN 5 5.0 5923 testPriorityN 5 5.0 5924 testPriorityN 5 5.0 -- Aug 25, 2014 7:57:29 AM FINE PrioritySorter.Queue.Sorter Sorted 4 Buildable Items with Min Weight 5 and Max Weight 5 Aug 25, 2014 7:57:29 AM FINER PrioritySorter.Queue.Sorter Queue: -- Item Id Job Name Priority Weight -- 5921 testPriorityN 5 5.0 5922 testPriorityN 5 5.0 5923 testPriorityN 5 5.0 5924 testPriorityN 5 5.0 -- Aug 25, 2014 7:57:29 AM FINE PrioritySorter.Queue.Items Starting: Id: 5921, JobName: testPriorityN, jobGroupId: 0, reason: , priority: 5, weight: 5.0, status: BUILDABLE Aug 25, 2014 7:57:29 AM FINE PrioritySorter.Queue.Sorter Sorted 3 Buildable Items with Min Weight 5 and Max Weight 5 Aug 25, 2014 7:57:29 AM FINER PrioritySorter.Queue.Sorter Queue: -- Item Id Job Name Priority Weight -- 5922 testPriorityN 5 5.0 5923 testPriorityN 5 5.0 5924 testPriorityN 5 5.0 -- Aug 25, 2014 7:57:32 AM FINE PrioritySorter.Queue.Sorter Sorted 3 Buildable Items with Min Weight 5 and Max Weight 5 Aug 25, 2014 7:57:32 AM FINER PrioritySorter.Queue.Sorter 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand commented on JENKINS-22294 Priority is not used in the scheduling I don't think the Throttle plugin or not allowing parallel executioin would work for me. I have 100 executors that can execute my build and I always have 50 jobs in queue and I want to somehow say "run this job in next possible slot". Or always run these jobs before those jobs. 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Marcus Müller commented on JENKINS-22294 Priority is not used in the scheduling Hi Magnus, thank you very much for investigating this issue. As I will keep working with your plugin the next weeks and months I will definitivily try out your latest version and post the results of what exteded logging tells me. Workaround: With your help I was able to find two simple workarounds. You told me to activate parallel builds in the job settings. This results in the job being build, guess?,...in parallel. Thus, no queue was created for me anymore, as all jobs were build at the same time. The first solution, which is obviously not the best, was to reduce the number of processors in the Jenkins settings. As this number represents the number of Jobs being build in parallel, as every core usually is capable to compute one of them. The more advanced solution is to install the Throttle Concurrent Builds Plug-in which allows you to set this limitation PER JOB. Reducing this throttle setting to 1 and allowing parallel builds got me the behaviour I expected. Now I can trigger Jobs (especially the same job multiple times) with a priority parameter and they are getting queued as expected with only one job build at a time. With best regards, Marcus 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Magnus Sandberg commented on JENKINS-22294 Priority is not used in the scheduling The later problem (from Marcus) is how it works as the Items to in Blocked mode and is therefore not actually in the queue and cannot be scheduled. The problem for witch this issues is created still looks strange and I haven't been able to reproduce it, are you maybe using another plugin also implementing a QueueSorter? In just released 2.7 I have added more logging used to print the Queue after it is sorted, this will tell you id the PrioritySorter indeed is sorting the way you expect. Please turn on this logging and see if that tells you anything. 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Marcus Müller commented on JENKINS-22294 Priority is not used in the scheduling Hi Magnus, Hi Markus, I am facing similar problems like described above. Starting the same job with different priorities via GUI or via POSTing URL results in a queue which is processed in the same order I added them with no respect to any priorities applied. Here is the log: Jun 11, 2014 2:32:19 PM FINER PrioritySorter.Queue.Items New Item: Id: 41, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: WAITING Evaluating JobGroup 0 ... Evaluating View All ... Not using filter ... Evaluating strategies ... Evaluating strategy Use Priority from Build Parameter ... Strategy is applicable Jun 11, 2014 2:32:19 PM FINE PrioritySorter.Queue.Items Buildable: Id: 41, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: BUILDABLE Jun 11, 2014 2:32:19 PM FINE PrioritySorter.Queue.Items Starting: Id: 41, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: BUILDABLE Jun 11, 2014 2:32:26 PM FINER PrioritySorter.Queue.Items New Item: Id: 42, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: WAITING Evaluating JobGroup 0 ... Evaluating View All ... Not using filter ... Evaluating strategies ... Evaluating strategy Use Priority from Build Parameter ... Strategy is applicable Jun 11, 2014 2:32:26 PM FINE PrioritySorter.Queue.Items Blocking: Id: 42, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: BLOCKED Jun 11, 2014 2:32:34 PM FINER PrioritySorter.Queue.Items New Item: Id: 43, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: WAITING Evaluating JobGroup 0 ... Evaluating View All ... Not using filter ... Evaluating strategies ... Evaluating strategy Use Priority from Build Parameter ... Strategy is applicable Jun 11, 2014 2:32:34 PM FINE PrioritySorter.Queue.Items Blocking: Id: 43, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: BLOCKED Jun 11, 2014 2:32:39 PM FINE PrioritySorter.Queue.Items Buildable: Id: 42, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: BUILDABLE Jun 11, 2014 2:32:39 PM FINE PrioritySorter.Queue.Items Starting: Id: 42, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: BUILDABLE Jun 11, 2014 2:32:51 PM FINER PrioritySorter.Queue.Items New Item: Id: 44, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: WAITING Evaluating JobGroup 0 ... Evaluating View All ... Not using filter ... Evaluating strategies ... Evaluating strategy Use Priority from Build Parameter ... Strategy is applicable Jun 11, 2014 2:32:51 PM FINE PrioritySorter.Queue.Items Blocking: Id: 44, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: BLOCKED Jun 11, 2014 2:32:59 PM FINE PrioritySorter.Queue.Items Buildable: Id: 43, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: BUILDABLE Jun 11, 2014 2:32:59 PM FINE PrioritySorter.Queue.Items Starting: Id: 43, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: BUILDABLE Jun 11, 2014 2:33:29 PM FINE PrioritySorter.Queue.Items Buildable: Id: 44, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: BUILDABLE Jun 11, 2014 2:33:29 PM FINE PrioritySorter.Queue.Items Starting: Id: 44, JobName: PrioTest, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: BUILDABLE With best regards, Marcus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Magnus Sandberg commented on JENKINS-22294 Priority is not used in the scheduling If you are submitting the same Job several times with different priorities you must also allow parallel execution of that Job. If you do not only one build will actually be in the queue, the rest will be in blocked state and can not be sorted by the PrioritySorter. Could this be the problem? 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Magnus Sandberg assigned JENKINS-22294 to Magnus Sandberg Priority is not used in the scheduling Change By: Magnus Sandberg (26/Mar/14 9:43 AM) Assignee: bklarson MagnusSandberg 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand commented on JENKINS-22294 Priority is not used in the scheduling No that is not the problem in this case. I have parallel execution allowed. I have only one executor that is able to execute the job. I also tested with two jobs running on the same executor, one with high and one with low priority. Both are equally executed. 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Magnus Sandberg commented on JENKINS-22294 Priority is not used in the scheduling OK, please turn on some logging as described on the wiki, this will tell exactly what priorities are used and when (and why) jobs are moved to the executor. 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand commented on JENKINS-22294 Priority is not used in the scheduling I have two jobs test_priority_high (priority: 1) and test_priority_low (priority: 5) both do "sleep 70" and build periodically (* * * * *) which means that there is always one of each in the queue. Both jobs are forced to running on the same executor. I would expect that only the test_priority_high would be executed as it has higher priority and there is always one in the queue when the executor is free. Not the jobs are run in the order in which they are started. This is what the log says (started with FINE but switched to FINER): New Item: Id: 13626, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: WAITING Mar 27, 2014 7:25:51 AM FINE PrioritySorter.Queue.Items New Item: Id: 13627, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: WAITING Mar 27, 2014 7:25:51 AM FINE PrioritySorter.Queue.Items Buildable: Id: 13626, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: BUILDABLE Mar 27, 2014 7:25:51 AM FINE PrioritySorter.Queue.Items Buildable: Id: 13627, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: BUILDABLE Mar 27, 2014 7:26:01 AM FINE PrioritySorter.Queue.Items Starting: Id: 13626, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: BUILDABLE Mar 27, 2014 7:26:51 AM FINE PrioritySorter.Queue.Items New Item: Id: 13628, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: WAITING Mar 27, 2014 7:26:51 AM FINE PrioritySorter.Queue.Items Buildable: Id: 13628, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: BUILDABLE Mar 27, 2014 7:27:16 AM FINE PrioritySorter.Queue.Items Starting: Id: 13627, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: BUILDABLE Mar 27, 2014 7:27:51 AM FINE PrioritySorter.Queue.Items New Item: Id: 13629, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: WAITING Mar 27, 2014 7:27:51 AM FINE PrioritySorter.Queue.Items Buildable: Id: 13629, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: BUILDABLE Mar 27, 2014 7:28:26 AM FINE PrioritySorter.Queue.Items Starting: Id: 13628, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: BUILDABLE Mar 27, 2014 7:28:51 AM FINER PrioritySorter.Queue.Items New Item: Id: 13630, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: WAITING Using priority taken directly from the Job Mar 27, 2014 7:28:51 AM FINE PrioritySorter.Queue.Items Buildable: Id: 13630, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: BUILDABLE Mar 27, 2014 7:29:39 AM FINE PrioritySorter.Queue.Items Starting: Id: 13629, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: BUILDABLE Mar 27, 2014 7:29:51 AM FINER PrioritySorter.Queue.Items New Item: Id: 13631, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: WAITING Using priority taken directly from the Job Mar 27, 2014 7:29:51 AM FINE PrioritySorter.Queue.Items Buildable: Id: 13631, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: BUILDABLE Mar 27, 2014 7:30:49 AM FINE PrioritySorter.Queue.Items Starting: Id: 13630, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: BUILDABLE Mar 27, 2014 7:30:51 AM FINER PrioritySorter.Queue.Items 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/d/optout.
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand created JENKINS-22294 Priority is not used in the scheduling Issue Type: Bug Affects Versions: current Assignee: bklarson Components: prioritysorter Created: 21/Mar/14 9:15 AM Description: When using build paramater set on the main config (http://master:8080/advanced-build-queue/?) "BuildPriority" and in the job set it in the job config the same parameter When running the build with parameteres the job is still executed in the starting order even when the priority goes from 5,4,3,2,1 The build queue shows them in right order. It is the execution that happens in wrong order Environment: Windows2012Server Jenkins LTS 1.532 Java7 Project: Jenkins Priority: Major Reporter: Markus Strand 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/d/optout.
