docs: the swarm-builder status gates the merge now, and no promise about rebasing a PR branch
This commit is contained in:
parent
2ea8c9de60
commit
5814f177c8
1 changed files with 9 additions and 7 deletions
|
|
@ -191,7 +191,8 @@ metrics it exports and the threat model:
|
|||
The swarm builder, in a `swarm-builder` container on the host that sets
|
||||
`deploy.builder.enable`; set it to `false` to opt out. It evaluates and builds
|
||||
unreviewed agent config PRs, and the result shows as a `swarm-builder` commit
|
||||
status on the PR. A red status blocks nothing: the merge still deploys. It also
|
||||
status on the PR. The status is required: a red or missing one blocks the
|
||||
merge. It also
|
||||
builds each agent before the swarm sends its deploy, and a failed build holds
|
||||
that deploy back. The jobs show on the swarm UI's Jobs page. It builds through
|
||||
its host's nix daemon, so it costs real CPU and disk.
|
||||
|
|
|
|||
Loading…
Reference in a new issue