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
1 changed files with 1027 additions and 148 deletions
|
|
@ -443,11 +443,6 @@ pub(super) async fn post_webhook_forge(
|
|||
}
|
||||
}
|
||||
DeliveryKind::VcsActivity => {
|
||||
if crate::meta_flake::moves_hyperhive(&body)
|
||||
&& let Err(e) = crate::jobq::queue_meta_update(&state.jobq)
|
||||
{
|
||||
tracing::warn!(error = %format!("{e:#}"), "webhook: queueing update_meta failed");
|
||||
}
|
||||
if let Some(activity) = crate::vcs_metrics::parse_push(&body) {
|
||||
crate::vcs_metrics::record_push(&activity);
|
||||
} else {
|
||||
|
|
|
|||
Loading…
Reference in a new issue