Skip to content

[Backport release-25.05] workflows: use cachix consistently#435321

Merged
wolfgangwalther merged 7 commits intorelease-25.05from
backport-435294-to-release-25.05
Aug 20, 2025
Merged

[Backport release-25.05] workflows: use cachix consistently#435321
wolfgangwalther merged 7 commits intorelease-25.05from
backport-435294-to-release-25.05

Conversation

@nixpkgs-ci
Copy link
Copy Markdown
Contributor

@nixpkgs-ci nixpkgs-ci bot commented Aug 20, 2025

Bot-based backport to release-25.05, triggered by a label in #435294.

  • Before merging, ensure that this backport is acceptable for the release.
    • Even as a non-committer, if you find that it is not acceptable, leave a comment.

This allows setting up a custom cachix cache in a contributor's fork.
That's most valuable when working on CI itself, testing and interating
in a fork. It's required when working on cachix related features
directly.

(cherry picked from commit 0254249)
Pushing the source path to cachix is pointless, because the only source
we're using is Nixpkgs - and that will always be available already via
checkout. No need to ever substitute it, so no need to push it either.

(cherry picked from commit 2400bdf)
For PRs targeting a fast moving branch like master, it might not
actually help because the merge commit will still be different on each
run. But on slower moving branches or when testing in a fork, it can
speed things up.

Since each of these build results is only a few hundred bytes without
any dependencies, it has essentially no cost.

Not adding this to `treefmt`, because this looks at *all* the files in
the repo, so needs to re-run even when iterating on CI only.

(cherry picked from commit 6ee40e7)
Speeds up evaluation a bit, because `filtered head` doesn't need to be
evaluated 3x.

(cherry picked from commit c4fa63d)
nixpkgs-vet doesn't care about our CI infrastructure, so ignoring these
files will lead to more cache hits when iterating on CI related PRs.

(cherry picked from commit 4d996cf)
At this stage, this only allows faster iteration when working on CI in
forks.

(cherry picked from commit 795dd01)
By definition the tarball changes on every commit, so it makes no sense
to cache it - it will just waste disk space.

(cherry picked from commit ac93865)
@nixpkgs-ci nixpkgs-ci bot mentioned this pull request Aug 20, 2025
2 tasks
@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux. 6.topic: continuous integration Affects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions 4.workflow: backport This targets a stable branch 6.topic: policy discussion Discuss policies to work in and around Nixpkgs and removed 6.topic: policy discussion Discuss policies to work in and around Nixpkgs 6.topic: continuous integration Affects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions 4.workflow: backport This targets a stable branch labels Aug 20, 2025
@wolfgangwalther wolfgangwalther merged commit db93f92 into release-25.05 Aug 20, 2025
58 of 62 checks passed
@wolfgangwalther wolfgangwalther deleted the backport-435294-to-release-25.05 branch August 20, 2025 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant