DevOps / Bamboo: Continuous Integration & Deployment Interview Questions
How does Bamboo handle parallel job execution?
Within a single stage, every job is eligible to run at the same time, as long as there's an agent available whose capabilities satisfy that job's requirements. Bamboo's scheduler simply dispatches each pending job to the first free, matching agent — it doesn't force sequential execution unless the stage structure says so.
Two things gate real parallelism in practice:
- Agent count — three jobs in a stage still run one after another if only one agent is free.
- Stage boundaries — the next stage always waits for every job in the current stage to finish, so parallelism only exists inside a stage, not across stages.
This is why teams splitting a long test suite into three jobs (e.g. unit, integration, contract tests) see real wall-clock savings only if at least three agents with the right capabilities are actually available at once.
What actually limits how many jobs run in parallel within a stage?
Does real parallelism ever occur across different stages in the same plan?
More Related questions...
