ArchitectureDeploy pipeline
Queue and worker
Each service has one worker that runs its deploys one at a time, in order.
Each service has one worker. The worker runs the deploys of its service one at a time, in order.
1 / 5
| Mechanism | What it is | Rule |
|---|---|---|
| Deploy queue | The deploys of one service with the status queued | A deploy waits for its turn. |
| Deploy worker | A background task, one per service | Two deploys of one service never overlap. |
| Build slot | The right to build one image | The server runs --build-concurrency builds at a time (default 2). |
Only the newest deploy matters
A new deploy cancels the older deploys of the same service that wait in the queue. Their reason is superseded by dep-….
If a deploy waits in the queue, a restart request merges into that deploy. It adds no deploy, because that deploy starts with the current settings.