"Priorities are assigned top down by first match" does not work correctly

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: prioritysorter-plugin
    • Environment:
      Jenkins Priority Sorter Plugin 2.2

      jenkins-1.544-1.1.noarch
      java-1.7.0-openjdk-1.7.0.45-2.4.3.4.el6_5.x86_64
      Linux kera 2.6.32-431.1.2.0.1.el6.x86_64 #1 SMP Fri Dec 13 13:06:13 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

      Probably plugin incorrectly assigns priorities to jobs. I have a job in two views: Sonar and All (plugin configuration is in the screenshot). According to the description "priorities are assigned top down by first match" - the job should receive priority 4 (or 3 if user run build) but unfortunately always receives 3 (or 2 if user run build).

        1. config.xml
          6 kB
          Adam Gabryƛ
        2. configuration.png
          25 kB
          Adam Gabryƛ
        3. jenkins.advancedqueue.PriorityConfiguration.xml
          1 kB
          Adam Gabryƛ
        4. jenkins.advancedqueue.PrioritySorterConfiguration.xml
          0.7 kB
          Adam Gabryƛ
        5. jenkins-configure-priority-sorter.png
          12 kB
          Adam Gabryƛ
        6. logger-configuration.png
          7 kB
          Adam Gabryƛ

            Assignee:
            Magnus Sandberg
            Reporter:
            Adam Gabryƛ
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: