DevOps / Bamboo: Continuous Integration & Deployment Interview Questions
Explain the lifecycle of a Bamboo deployment?
A deployment starts only after a build plan has already produced a usable artifact; the deployment project then takes over from there.
flowchart TD
A[Build plan produces artifact] --> B[Release created in deployment project]
B --> C[Select target environment, e.g. Staging]
C --> D{Environment permission check}
D -- Denied --> E[Deployment blocked]
D -- Allowed --> F[Run environment's deployment tasks]
F --> G{Tasks succeed?}
G -- No --> H[Environment marked failed, rollback if configured]
G -- Yes --> I[Environment marked successful, status shown in Jira]
Two details matter for interviews: a release is a specific, immutable artifact version, and each environment keeps its own independent deployment history — Staging failing doesn't affect Production's last known state, and promoting to Production means running that same tested artifact through the Production environment's own tasks, not rebuilding it.
What starts the deployment lifecycle in Bamboo?
If a deployment to Staging fails, what happens to Production's last known state?
More Related questions...
