pin internal/meta's hyperhive on the controller's rev and rebuild agents when it moves
The swarm controller offers its own running rev (services.hyperhive.c0re. hyperhiveRev) as the hyperhive pin of internal/meta and takes it only when the forge compare API shows it descends from the committed pin; merges to hyperhive main no longer move the pin, and the first commit pins main's head. When a commit moves the pin, every placed agent gets a TriggerDeploy. A deploy after a meta update no longer waits on it succeeding (after_any), so a down builder does not hold back hives that render locally.
This commit is contained in:
parent
5950363a10
commit
22e2d30581
10 changed files with 1027 additions and 148 deletions
|
|
@ -95,7 +95,8 @@ Per-hive (host + in-container):
|
|||
utility crate.
|
||||
- **`hive-metric/`** — one-shot CLI pushing a labeled metric over OTLP.
|
||||
- **`hive-meta-flake/`** — the meta flake's `flake.nix` text, a pure
|
||||
render. hive-c0re and swarm-controller both call it.
|
||||
render, and the reads of its pins. hive-c0re and swarm-controller both call
|
||||
it.
|
||||
|
||||
Wire types + socket plumbing:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue