ci: build the nix job with Determinate Nix + FlakeHub cache - #17
Merged
Conversation
The nix job now pushes what it builds to the account's private FlakeHub cache and pulls prior builds back. Auth is the job's OIDC JWT (id-token: write) — account-scoped, no secret, no registration; fork PRs lack the token and simply build without the push. The test job keeps plain upstream Nix: it only evals (builtins-only fixture), so the cache buys nothing and skipping the login keeps fork PRs warning-free.
Contributor
Code Metrics Report
Details | | main (e1bc07c) | #17 (030c9fb) | +/- |
|---------------------|----------------|---------------|------|
| Coverage | 94.9% | 94.9% | 0.0% |
| Files | 30 | 30 | 0 |
| Lines | 3795 | 3795 | 0 |
| Covered | 3603 | 3603 | 0 |
| Test Execution Time | 5s | 5s | 0s |Reported by octocov |
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
1 participant
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.
The
nixjob (nix flake check -L) now runs on Determinate Nix withflakehub-cache-action: everything it builds lands in the account's private FlakeHub cache and later runs pull it back.id-token: write) — the cache is account-scoped, so there's no secret and no per-repo registration.testjob stays on plain upstream Nix deliberately — it only evals the builtins-only fixture (no builds to cache), and skipping the FlakeHub login keeps fork PRs warning-free. Comment updated to say so.Part of wiring FlakeHub cache across kriswill/* repos (see kriswill/dotfiles#35).