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

Upstream job priority ignored

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • prioritysorter-plugin
    • None
    • CentOS6, Jenkins 2.32.2, PrioritySorter 3.5.0

    Description

      Priority sorter global configuration:

      • Strategy: Absolute
      • Number of priorities: 5
      • Default priority: 3

      Job priorities: A single job group:

      • Jobs to include: All
      • Priority: Default
      • Use additional rules when assigning a priority to a Job: checked
        • Job Triggered by a Upstream Build (" Use the same priority as assigned to the Upstream Build that caused this Jobs to start.")
        • Job Triggered by a User: Priority 1

      Jobs:

      • "A" (upstream), triggering "B" via Parameterized Trigger Plugin with "Block until the triggered projects finish their builds" checked
      • "B" (downstream)

      With this configuration, I'd expect that job "B" gets scheduled with priority 1, if "A" was started manually. Or am I wrong? However, it runs with the default priority according to the logs. The same happens if "B" gets started from "A" from a post-build step ("Build other projects").

      The plugin correctly recognizes that "B" was triggered by "A" ("Job Triggered by a Upstream Build"), but cannot determine the priority correctly.

      Attachments

        Activity

          rschuetz Ronny Schuetz created issue -
          rschuetz Ronny Schuetz made changes -
          Field Original Value New Value
          Description Priority sorter global configuration:
           * Strategy: Absolute
           * Number of priorities: 5
           * Default priority: 3

          Job priorities: A single job group:
           * Jobs to include: All
           * Priority: Default
           * Use additional rules when assigning a priority to a Job: checked
           ** Job Triggered by a Upstream Build (" Use the same priority as assigned to the Upstream Build that caused this Jobs to start.")
           ** Job Triggered by a User: Priority 1

          Jobs:
          * "A" (upstream), triggering "B" via Parameterized Trigger Plugin with "Block until the triggered projects finish their builds" checked
          * "B" (downstream)

          With this configuration, I'd expect that job "B" gets scheduled with priority 1, if "A" was started manually. Or am I wrong? However, it runs with the default priority according to the logs. The same happens if "B" gets started from "A" from a post-build step ("Build other projects").

          The plugin correctly recognizes that "B" was triggerd by "A" ("Job Triggered by a Upstream Build"), but cannot determine the priority.




          Priority sorter global configuration:
           * Strategy: Absolute
           * Number of priorities: 5
           * Default priority: 3

          Job priorities: A single job group:
           * Jobs to include: All
           * Priority: Default
           * Use additional rules when assigning a priority to a Job: checked
           ** Job Triggered by a Upstream Build (" Use the same priority as assigned to the Upstream Build that caused this Jobs to start.")
           ** Job Triggered by a User: Priority 1

          Jobs:
          * "A" (upstream), triggering "B" via Parameterized Trigger Plugin with "Block until the triggered projects finish their builds" checked
          * "B" (downstream)

          With this configuration, I'd expect that job "B" gets scheduled with priority 1, if "A" was started manually. Or am I wrong? However, it runs with the default priority according to the logs. The same happens if "B" gets started from "A" from a post-build step ("Build other projects").

          The plugin correctly recognizes that "B" was triggered by "A" ("Job Triggered by a Upstream Build"), but cannot determine the priority correctly.




          rschuetz73 Ronny Schuetz made changes -
          Assignee Magnus Sandberg [ emsa23 ] Ronny Schuetz [ rschuetz73 ]
          rschuetz73 Ronny Schuetz made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          rschuetz Ronny Schuetz made changes -
          Status In Progress [ 3 ] In Review [ 10005 ]
          rschuetz73 Ronny Schuetz made changes -
          Resolution Fixed [ 1 ]
          Status In Review [ 10005 ] Resolved [ 5 ]
          markewaite Mark Waite made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

          People

            rschuetz73 Ronny Schuetz
            rschuetz Ronny Schuetz
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: