Repository navigation
ci: Agent Dev builds nightly, EIF builds on 16 vCPU, Windows build on Blacksmith - #1341
Merged
Merged
Conversation
Agent master pushes now build, sign and verify only Prod on macOS, Linux and Windows. Dev packages build nightly on the master tip (10:37 UTC) and, with Prod, on a manual dispatch. The Dev legs cost about $1.50 per Agent push. They also coupled the chains: on 0.0.12 (run 40625776561) 'Linux bundle (dev)' lost its runner, and Attest and Verify Linux were skipped for Prod too, so the release could not publish Linux without a rerun. Pushes no longer have a Dev leg to wait for. - Every packaging job's variant matrix is Prod on push, Dev on schedule and both on dispatch; each job's if: admits the schedule event. The changes job already selects the build on any non-push event. - Dev and Prod share the exact-key release cache (the profile changes only Agent workspace crates). Only pushes save it, so the nightly and dispatched builds restore Prod's entry and never write it. - The publisher already rejects schedule runs; desktop-signing and windows-signing allow master by branch policy, which a scheduled run on the default branch satisfies. - C2 now checks every event: a push that drops Prod or builds Dev, or a nightly that builds Prod, fails. C4 evaluates the release-cache save condition per event (push only) and pins its writers to Prod on push. - test_plan covers the nightly selection; docs updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The os-eif PR candidate is the one thing keeping OpenSecret src/ PRs over 10 minutes: its build took p50 7.8 / p90 9.2 min on 8 vCPU ARM (52 dev+prod pairs, 10-11..10-26), so ci-ok on PRs with EIF inputs was ~9.9 p50 / 12.4 p90 and 44% of them exceeded 10 min. Every EIF builder moves together, so the PR candidate, the trusted master and approval builds and the release builder stay on one runner class (C5): lanes.py EIF_BUILDER (ci.yml os-eif), opensecret-eif.yml eif-trusted and opensecret-eif-release.yml build. actionlint declares the new label in place of the old one, which nothing uses any more. The unprivileged fork job stays on GitHub's ubuntu-24.04-arm. Nothing else about the EIF builds, their inputs or the PCR checks changes. 16 vCPU ARM costs twice the rate for an expected ~0.6x the time, about +24% per build. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
'Build Windows binary' moves from maple-windows-2025-16core back to blacksmith-8vcpu-windows-2025. The fat-LTO link runs on one thread, so the 16-core runner is no faster warm (19.7 min of Cargo against 19.4-20.8 on Blacksmith) and costs about $1.05 more per Agent push, roughly $300 a month. Signing and verification stay on GitHub's windows-2025. Kept consistent with what #1333 changed alongside it: - test_workflow_policy no longer lists the job as a GitHub cache-store writer; its exact-key release cache now lives in Blacksmith's store, like the macOS and Linux builders'. The first Windows build after this lands starts cold once; nothing else reads that key. - actionlint keeps maple-windows-2025-16core (release.yml and ci.yml still use it) and already declares the Blacksmith label. - The signature probe keeps accepting all three build runners, since it checks historical producer runs; only its comment changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
C2 now pins that the publisher rejects the nightly run by its event, even when the run carries every Prod job and artifact. The Agent README and the publisher docs describe which runs build and which qualify. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AnthonyRonning
added a commit
that referenced
this pull request
Oct 28, 2026
#1339 changed the CodeQL release rule, #1337 made packaging rehearsals label-only and gave them a nightly-saved cache, and #1341 left the EIF runner comment broader than C5. Older: the nightly does not run every lane, the Research hook runs no Clippy, and the Agent lane tests no longer cover a benchmark. The CI skill now says comments and docs move with behaviour in the same PR. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Saves about $680 a month on Agent runners. OpenSecret PRs that change the enclave image get an estimated ~3 min faster. A Dev build failure can no longer block a Prod release.
blacksmith-16vcpu-ubuntu-2404-arm.Build Windows binaryjob moves back toblacksmith-8vcpu-windows-2025. It is just as fast warm (fat-LTO link on one thread), and about $1.05 a push cheaper.Proven only after merge:
Local checks pass:
plan.py lint, the scripts/ci suite (511), the publisher tests (133), the release gates and actionlint. Full notes are in the session notes (impl2-notes.md).🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.