swarm builder: the all-swarm-services switch turns it on, like every other swarm service
deploy.builder.enable defaults on under deploy.allSwarmServices (mkDefault), where the host has the builder's store identity pair, as for the review classifier. An explicit false still wins.
This commit is contained in:
parent
5b49e0e539
commit
d24dbaeadf
7 changed files with 68 additions and 26 deletions
|
|
@ -268,9 +268,11 @@ the container and the threat model are in
|
|||
### Builder
|
||||
|
||||
The swarm builder, in a `swarm-builder` container on the host that sets
|
||||
`deploy.builder.enable`. It doesn't derive from `allSwarmServices`: it
|
||||
evaluates and builds unreviewed config PRs through its host's nix daemon, so
|
||||
running one is a decision of its own, as for the CI runner.
|
||||
`deploy.builder.enable`. `allSwarmServices` defaults it on wherever the host
|
||||
has the builder's store identity, as for the review classifier below: the host
|
||||
that runs the store has it. Set `deploy.builder.enable = false` to opt out. It
|
||||
evaluates unreviewed config PRs and builds them through its host's nix daemon,
|
||||
from a container with its own network namespace.
|
||||
|
||||
When an `agent-configs/<agent>` PR opens, reopens or gets a new push,
|
||||
swarm-controller queues a `build_agent` job. Jobs run one at a time, and a
|
||||
|
|
|
|||
Loading…
Reference in a new issue