[JIRA] [prioritysorter-plugin] (JENKINS-24618) Absolute priority not working
Magnus Sandberg closed JENKINS-24618 as Cannot Reproduce Absolute priority not working Not been able to reproduce. As far as I can see in the logs I have received the Queue Sorter was never invoked properly. Possible reasons for this is Java 7 incompatibility (now fixed) or usage of more than one Sorter (not supported in Jenkins) Please open new issue if problem persists include logs on FINER as described on the wiki. Thanks Change By: Magnus Sandberg (02/May/15 7:52 PM) Status: Open Closed Resolution: Cannot Reproduce 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-plugin] (JENKINS-24618) Absolute priority not working
Paul Draper commented on JENKINS-24618 Absolute priority not working @Magnus, my apologies. I mistakenly believed that a higher priority number meant a higher priority. In fact, it is actually the opposite: a higher priority number means a lower priority. So my testing was backwards. It does indeed work for me. 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-plugin] (JENKINS-24618) Absolute priority not working
Magnus Sandberg commented on JENKINS-24618 Absolute priority not working I have never actually been able to reproduce this. Please turn on extensive logging as described on the wiki, it will tell you how and why a jobs gets a certain priority. If you then can see that something is misbehaving and give me some logs I'm happy to investigate. 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-plugin] (JENKINS-24618) Absolute priority not working
Paul Draper commented on JENKINS-24618 Absolute priority not working This issue is now over six months old. Is there a version I can downgrade to where the plugin works? Did it ever work? 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-plugin] (JENKINS-24618) Absolute priority not working
Markus commented on JENKINS-24618 Absolute priority not working Hi Pedro, I am not the expert on this plugin. But for us, some jobs are in multiple views. It seems that the Job Priorities (advanced-build-queue) starts at the top and when a job matches a criteria, it gets that priority. It does not matter if the jobs is in other views further down in the list. We use regular expressions for the views, but some priorities are set using the Job Priorities criteria. Such as manually started jobs. We don't have any priorities set up for individual jobs, those are all removed. I do not know if that is required. We have also disabled "allow priorities directly on Jobs". I do not know if that is required. 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-plugin] (JENKINS-24618) Absolute priority not working
pedro reis commented on JENKINS-24618 Absolute priority not working Markus, to set via "Job Priorities" (aka http://jenkins:8080/advanced-build-queue/) you have to have all the jobs with the same priority in the same view? Did you use regular _expression_ to filter them? Before using "Job Priorities" do you have to clean up the priority of each job? Do you have to unset " Allow priorities directly on Jobs" at "Configure System" (http://jenkins:8080/configure)? Thanks in advance. 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-plugin] (JENKINS-24618) Absolute priority not working
pedro reis commented on JENKINS-24618 Absolute priority not working Hi, We are also having this issue. Jenkins 1.565.3 ; priority sorter 2.9 . We're using "Absolute", and "Allow priorities directly on Jobs" so we set the priorities in each job. (each job has sub-jobs with different configurations, aka matrix) We have a python script that starts several jobs. Priority isn't always being respected. What is the threshold time that the jobs delay before starting? (I image there is such a delay, to allow other jobs with bigger priority to start before them) 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.
