5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	3f8b0b4248	Build modules take asks only within their node's build hours ... mesh-build-go, -node and -image declare build-hours (node=HH:MM-HH:MM in the node's local time, empty = any hour) and hand it to the SDK puller (the operator, 2026-10-26: g14 builds only from 18:00 to 06:00); their SDK pin moves to mesh-sdk d00dac1, which has it.	2026-10-26 21:22:09 +01:00
jschoubben	245143d948	Build modules run at most as many steps as their node's build CPU gives, and say a check's phases ... Each of mesh-build-go, -node and -image declares cores-per-step (6, 2, 2) and hands it to the SDK puller, which bounds the configured capacity by floor(slice quota cores / cores-per-step), read live; thread limits and the status tools follow the effective capacity (issue 1806's follow-up: three Go checks on shanks' 12-core slice starved past the 30-minute step bound). mesh-build-go says its lint and test phases with the ask id (issue 1890).	2026-10-26 19:55:31 +01:00
jschoubben	c304d3fb97	Pull the image build seat's asks beside the tools, at most the node's capacity (issue 1887 A3image, ADR 0525 §2-§6)	2026-10-23 15:40:43 +02:00
jschoubben	9e2d1164f0	Give mesh-build-image the registry's address as the seat's reach, which the provisioner's client fills (issue 1703)	2026-10-22 11:07:50 +02:00
jschoubben	692fc3e1ab	Add mesh-build-image: rootless image builds with buildah, pushed by tag from trunk only (issue 1703)	2026-10-22 10:27:01 +02:00