Watch
0
0
Fork
You've already forked hyperhive
0

queue the meta update only until one run succeeds

This commit is contained in:
atlas 2026-10-25 12:56:30 +01:00
commit 31cb6bfa42
2 changed files with 91 additions and 32 deletions

View file

@ -143,8 +143,9 @@ running rev (`services.hyperhive.c0re.hyperhiveRev`, from `self.rev`):
The controller commits `flake.nix` and the returned `flake.lock` to
`internal/meta` in one commit, and gives each hive's forge account read on the
repo. It re-renders when it starts and every ten minutes after (a tick skips
while an update is pending or running), before it deploys a merged config PR, and
repo. It re-renders when it starts, and again every ten minutes while the latest
update hasn't succeeded (a tick adds nothing while one is pending or running,
or after a success), before it deploys a merged config PR, and
before the first deploy of a new agent. Those deploys run whether or not the
update succeeded: a hive that builds from `internal/meta` does so only while it
pins the agent's current config (see