ci: Add workflow to seed cachix #2615
Merged
Conversation
This file contains 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
robx
force-pushed
the
seed-cachix
branch
3 times, most recently
from
0972974 to
d944eed
Compare
This was referenced Jan 16, 2023
Merged
steve-chavez
approved these changes
Jan 16, 2023
laurenceisla
pushed a commit
to laurenceisla/postgrest
that referenced
this pull request
Apr 11, 2023
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.
This is broken out of #2612; subsumes #2611.
The idea is to have a dedicated workflow to incrementally seed cachix, which can be manually triggered on appropriate pull requests. E.g., when a nixpkgs update or dependency update PR is "ready" but stuck due to CI timing out, we'd manually trigger this workflow to push build results to cachix incrementally.
For the moment, the workflow is run automatically on PR, but that's just for this PR, to be removed before merging.
(There's the same outstanding issue as with #2611, in that building
postgrest-push-cachixalso causes a build ofcabal2nix-postgrestfor no good reason. But currently that justs causes a bit of unnecessary extra work, so maybe we can leave that for later.)