DevOps / Bamboo: Continuous Integration & Deployment Interview Questions
Explain the internal working of Bamboo agent-server communication?
Agents don't wait for the server to push work to them blindly — the relationship is closer to agents checking in and the server assigning work from a queue.
sequenceDiagram
participant S as Bamboo Server
participant A as Remote Agent
A->>S: Register / heartbeat (capabilities, status)
S->>S: Queue job, match against agent capabilities
S->>A: Assign job
A->>S: Request job details, artifacts
A->>A: Execute tasks
A->>S: Stream logs and status incrementally
A->>S: Report final result (success/failure)
S->>S: Update build results, trigger next stage if applicable
The connection is typically a persistent, authenticated channel over HTTPS. If it drops, the agent shows as offline and any job it was mid-way through is marked as failed/interrupted rather than silently left in limbo, since the server has no way to confirm the work actually completed.
What happens to a running job if its agent's connection to the server drops mid-build?
What does an agent send to the server as part of its ongoing communication?
More Related questions...
