Build KEVM once per architecture in release, populate both nix caches from it#2860
Merged
Merged
Conversation
…caches from it Merge the 'Populate Nix Cache' and 'Populate Nix Binary Cache' release jobs into a single 'nix-cache' job that builds KEVM once per architecture and pushes the resulting store paths to both the public k-framework cache and the private k-framework-binary cache. Previously each cache had its own job, so KEVM was built twice per architecture (four builds total), doubling release-time build pressure. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
anvacaru
approved these changes
Jun 10, 2026
automergerpr-permission-manager
Bot
merged commit 5388c8d
into
master
23 of 24 checks passed
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
2 participants
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.
Same idea as: runtimeverification/k#4927
The release workflow had two separate jobs —
nix-cache("Populate Nix Cache") andnix-binary-cache("Populate Nix Binary Cache") — that each independently built KEVM on anormal+ARM64matrix. That meant KEVM was compiled four times per release (twice per architecture), doubling build pressure for no benefit: nix is content-addressed, so once.#kevmis realized in the local store, both thecachix push(publick-framework) andkup publish(privatek-framework-binary) steps just push the already-built paths.This merges the two into a single
nix-cachejob that builds once per architecture and populates both caches, each with its own auth token.Changes:
nix-binary-cacheintonix-cache: thekup publish k-framework-binarystep now runs as a third step after the public-cache push, sharing the singlenix build.CACHIX_AUTH_TOKENpreserved (publicCACHIX_PUBLIC_TOKENfor thek-frameworkpush, privateCACHIX_PRIVATE_KFB_TOKENfor thek-framework-binarypublish).nix-binary-cachefrommake-release'sneeds(now[draft-release, nix-cache]).🤖 Generated with Claude Code