You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The expand step of the new label contract, on EC2 x64.
The webhook accepts an optional size label (ci-cpu-2, ci-cpu-4, ci-cpu-8, ci-cpu-16) and the architecture labelx64, for now defaulting to ci-cpu-4 and x64 when they're missing. Today's runs-on (self-hosted, ci-spot) keeps working unchanged.
The launcher launches the matching .large, .xlarge, .2xlarge or .4xlarge across m7i/m6i/m6a/m7a in the three subnets.
The launcher tags every runner with its shape (ci-runner:capacity, ci-runner:vcpus, ci-runner:arch).
make hand-launch takes a size.
arm64 is not accepted yet; that comes with "arm64 on EC2".
Acceptance criteria
Webhook tests cover every size; a job with two size labels, an unknown ci-cpu-*, or arm64 is outside the contract.
Launcher tests check the fleet overrides for each size and the shape tags.
Defaults hold: a job with only self-hosted and ci-spot launches a .xlarge, as today.
Proven live: one job at ci-cpu-8 runs on a .2xlarge.
README, docs/stack.md and the runbook describe the size labels.
Activity
Merge ticket #22: size labels on EC2 (expand), live proof pending
sodre commentedon Nov 14, 2026
Live (integration f3a7899):
[self-hosted, ci-spot, ci-cpu-8, x64]ran on i-078faca1ffb2527f4, an m6a.2xlarge (nproc 8): https://github.com/zeroae/ci-runner-canary/actions/runs/43541777893. The first .2xlarge was swapped onto a zae-zcm job and repaired.