3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	d94764f001	Build build-agent and route-proxy without a build ID (hq issue 721) ... Go's build ID hashes every input package, so a change mesh-builder never reaches still changed its bytes; without it, a rebuild of the same program is the same file, and the check can say the module is unchanged.	2026-10-14 21:07:26 +02:00
jochen	f4fb0a7461	Name the package each controller-repository image compiles, and say a renamed file under both names (hq ADR 0267, issue 363) ... Every merge to the controller's repository rebuilt the route proxy and the build seat's holder, because their builds read that repository whole. Named, the build seat hands each only its program's build source and the planner moves each only when that changes. A rename was said under its new name alone, so a file moved out of a build source changed nothing the planner could see.	2026-10-10 02:58:31 +02:00
jochen	84403aec0c	build-agent: the build machine as a node role every machine can hold (hq ADR 0190) ... 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.	2026-10-02 22:28:48 +02:00