DevOps / Bamboo: Continuous Integration & Deployment Interview Questions
How do you configure Bamboo to build Docker images?
Docker builds in Bamboo generally follow one of two patterns. The simpler one is a Script task on a remote agent that has Docker installed, running the standard build and push commands directly:
docker build -t registry.example.com/payments-api:${bamboo.buildNumber} . docker push registry.example.com/payments-api:${bamboo.buildNumber}
For this to work, the agent needs a Docker capability declared so the scheduler only routes the job there, and registry credentials stored as Bamboo variables (masked as passwords) rather than hard-coded in the script.
The other pattern runs the job's tasks inside a Docker container as the build environment itself, which keeps the toolchain isolated per plan rather than installed permanently on the agent host — useful when different plans need conflicting versions of the same tool.
Why declare a 'Docker' capability on the agent rather than assuming any agent can run the job?
Besides a script task running docker build, what's the other common Bamboo Docker pattern?
More Related questions...
