Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-24618

Absolute priority not working

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Cannot Reproduce
    • Component/s: prioritysorter-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.520, priority sorter 2.8
    • Similar Issues:

      Description

      We are seeing problems with ignored priorities in the plugin, so I decided to make the simplest test I could think of:

      Start a build on one machine with only one executor that runs for half a minute.
      While it is building, start 2 builds of jobs with varying absolute priorities set, 1 and 2.
      Watch in which order the other builds are run.

      Everytime I do this test, the builds are executed in FIFO order, with no concern of priority.
      If I repeat this test with the older priority mechanism of the plugin, it works like it should.

        Attachments

          Activity

          Hide
          mabahj Markus added a comment -

          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.

          Show
          mabahj Markus added a comment - 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.
          Hide
          draperp Paul Draper added a comment -

          This issue is now over six months old.

          Is there a version I can downgrade to where the plugin works?

          Did it ever work?

          Show
          draperp Paul Draper added a comment - This issue is now over six months old. Is there a version I can downgrade to where the plugin works? Did it ever work?
          Hide
          emsa23 Magnus Sandberg added a comment -

          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.

          Show
          emsa23 Magnus Sandberg added a comment - 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.
          Hide
          draperp Paul Draper added a comment -

          @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.

          Show
          draperp Paul Draper added a comment - @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.
          Hide
          emsa23 Magnus Sandberg added a comment -

          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

          Show
          emsa23 Magnus Sandberg added a comment - 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

            People

            Assignee:
            emsa23 Magnus Sandberg
            Reporter:
            t_westling Tomas Westling
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: