The builder's manifest with the one change that matters: it claims node-build-agent, a node seat, so it is assignable to every machine with a container runtime, and every holder pulls one build at a time from the role's one work queue (hq ADR 0190, design 18 "Where a build runs"). Same image recipe (compiled from the mesh-controller repository's main), same provisions, same workspace and credential.
Do not merge before the controller with ADR 0190's seat (node-build-agent, pull workers) has rolled — until then the catalogue check refuses an unknown seat. Then: register build-agent by building this path, assign it to every machine with a container runtime, unassign builder, and a follow-up PR removes modules/builder.
The builder's manifest with the one change that matters: it claims `node-build-agent`, a node seat, so it is assignable to every machine with a container runtime, and every holder pulls one build at a time from the role's one work queue (hq ADR 0190, design 18 "Where a build runs"). Same image recipe (compiled from the mesh-controller repository's main), same provisions, same workspace and credential.
**Do not merge before** the controller with ADR 0190's seat (`node-build-agent`, pull workers) has rolled — until then the catalogue check refuses an unknown seat. Then: register build-agent by building this path, assign it to every machine with a container runtime, unassign `builder`, and a follow-up PR removes `modules/builder`.
The builder's manifest with one change that matters: it claims node-build-agent, a node seat, so it
is assignable to every machine with a container runtime, and every holder pulls one build at a time
from the role's one work queue. A tier of many images is then built by as many machines as hold the
seat and are online. The builder module stays until this is assigned where it was; then it goes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The builder's manifest with the one change that matters: it claims
node-build-agent, a node seat, so it is assignable to every machine with a container runtime, and every holder pulls one build at a time from the role's one work queue (hq ADR 0190, design 18 "Where a build runs"). Same image recipe (compiled from the mesh-controller repository's main), same provisions, same workspace and credential.Do not merge before the controller with ADR 0190's seat (
node-build-agent, pull workers) has rolled — until then the catalogue check refuses an unknown seat. Then: register build-agent by building this path, assign it to every machine with a container runtime, unassignbuilder, and a follow-up PR removesmodules/builder.