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

proximally started jobs are not sorted correctly

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: prioritysorter-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.138.1 (on Linux Mint)
      Priority Sorter 3.6.0
    • Similar Issues:

      Description

      Jobs started almost simultaneously are not sorted by priority.  For example, a job with priority 1714 is running before a job with 1712 even though both were started within about a second of each other.  Both jobs are definitely queued and ready.  This happens regardless of the length of the quiet period.

      I see JENKINS-12994 which may be related somehow.  Perhaps this needs to be a configuration setting?  I DO need to be able to start multiple jobs quickly in a quiet period and then have the highest priority ones start, even if some have to wait for others to expire their quiet periods.  But if it's a problem in other situations, perhaps there could be a prioritizing wait period so that jobs won't sleep forever on pending jobs with longer quiet periods.

      Any other suggested workarounds?

        Attachments

          Activity

          einheber Patrick Einheber created issue -
          einheber Patrick Einheber made changes -
          Field Original Value New Value
          Description Jobs started almost simultaneously are not sorted by priority.  For example, a job with priority 1714 is running before a job with 1712 even though both were started within about a second of each other.  Both jobs are definitely queued and ready.  This happens regardless of the length of the quiet period.

          I see JENKINS-12994 which seems to introduce this undesirable behavior.  Perhaps this needs to be a configuration setting?  I DO need to be able to start multiple jobs quickly in a quiet period and then have the highest priority ones start, even if some have to wait for others to expire their quiet periods.  But if it's a problem in other situations, perhaps there could be a prioritizing wait period so that jobs won't sleep forever on pending jobs with longer quiet periods.

          Any other suggested workarounds?
          Jobs started almost simultaneously are not sorted by priority.  For example, a job with priority 1714 is running before a job with 1712 even though both were started within about a second of each other.  Both jobs are definitely queued and ready.  This happens regardless of the length of the quiet period.

          I see JENKINS-12994 which may be related somehow.  Perhaps this needs to be a configuration setting?  I DO need to be able to start multiple jobs quickly in a quiet period and then have the highest priority ones start, even if some have to wait for others to expire their quiet periods.  But if it's a problem in other situations, perhaps there could be a prioritizing wait period so that jobs won't sleep forever on pending jobs with longer quiet periods.

          Any other suggested workarounds?

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            einheber Patrick Einheber
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: