Ephemeral Containers
Every task runs in a fresh, ephemeral container — there’s no persistent build-agent state carried between runs.
If a task secretly depends on state left behind by a previous run, Concourse surfaces that immediately: the next run starts clean and just fails. That’s cheaper to catch in CI than in production, and it’s the same design goal behind Jenkins’s dynamic Kubernetes agents — a build environment that can’t accumulate drift because it doesn’t have a lifespan to drift over.
Related
- Jenkins: dynamic Kubernetes agents
- Setup & Sizing — worker-level resource limits matter more here because every task spins up a fresh container.