Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-12686

Queue for plan stages with one agent is not FIFO

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: Low Low
    • None
    • 4.3
    • Build Queues
    • None

    • OnDemand (4.3.2-rotp-4)

      In the situation where there is only one agent (which matches all capabilities and requirements of all plans), Bamboo will randomly pick a stage from all currently queued plans to run. For example,

      1. Plan A: Stage 1
      2. Plan B: Stage 1
      3. Plan B: Stage 2
      4. Plan A: Stage 2
      5. Plan A: Stage 3

      This is unintuitive behaviour. Bamboo should commit to FIFO ordering for plan stages in this situation.

            [BAM-12686] Queue for plan stages with one agent is not FIFO

            PiotrA added a comment -

            Seems another occurence of the same problem: https://answers.atlassian.com/questions/132780/stages-are-not-executed-atomically

            PiotrA added a comment - Seems another occurence of the same problem: https://answers.atlassian.com/questions/132780/stages-are-not-executed-atomically

            James Dumay added a comment -

            Hi there,

            This is not how Stages work. Jobs for successive stages are only queued when the previous Stage has successfully completed which means that the Jobs in the Stage that finishes first are queued first.

            One long term solution to this would be to provide priorities for the build queue so that Agents prefer running Jobs from Plan A first rather than running in the natural queue order. See BAM-3705.

            Thanks
            James

            James Dumay added a comment - Hi there, This is not how Stages work. Jobs for successive stages are only queued when the previous Stage has successfully completed which means that the Jobs in the Stage that finishes first are queued first. One long term solution to this would be to provide priorities for the build queue so that Agents prefer running Jobs from Plan A first rather than running in the natural queue order. See BAM-3705 . Thanks James

              Unassigned Unassigned
              mknight@atlassian.com Michael Knight
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: