DevOps / Bamboo: Continuous Integration & Deployment Interview Questions
Explain the execution flow of a Bamboo Specs YAML file?
A Specs YAML file goes through a detect-validate-apply cycle rather than being executed directly like a script.
flowchart TD
A[bamboo-specs.yml committed to repository] --> B[Bamboo scans linked repository for Specs]
B --> C[Parse and validate YAML structure]
C --> D{Valid?}
D -- No --> E[Publication fails, error shown in Bamboo]
D -- Yes --> F[Create or update matching plan definition]
F --> G[Apply stages, jobs, tasks, triggers, permissions]
G --> H[Plan/branch ready to build on next trigger]
A minimal example:
version: 2 plan: project-key: PAY key: PAYAPI stages: - Build: jobs: - Compile: tasks: - checkout - maven: 'clean install'
Because this is a publish-and-validate step rather than a build step itself, a broken Specs file fails fast with a clear parsing error in Bamboo's UI, before any agent ever picks up work — it never silently produces a half-configured plan.
What happens when Bamboo detects an invalid Specs YAML file?
How does Bamboo discover a Specs YAML file in the first place?
More Related questions...
