-
Bug
-
Resolution: Answered
-
Low
-
None
-
4.3
-
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,
- Plan A: Stage 1
- Plan B: Stage 1
- Plan B: Stage 2
- Plan A: Stage 2
- 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
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1434068 ] | New: JAC Bug Workflow v3 [ 3378431 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1407821 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1434068 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 609899 ] | New: Bamboo Workflow 2016 v1 [ 1407821 ] |
Workflow | Original: Bamboo Workflow 2014 [ 604361 ] | New: Bamboo Workflow 2014 v2 [ 609899 ] |
Workflow | Original: Bamboo Workflow 2010 [ 460074 ] | New: Bamboo Workflow 2014 [ 604361 ] |
Remote Link | New: This issue links to "stages-are-not-executed-atomically (Web Link)" [ 35324 ] |
Resolution | New: Answered [ 9 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Seems another occurence of the same problem: https://answers.atlassian.com/questions/132780/stages-are-not-executed-atomically