Add caching for Nix in CI workflow#191
Closed
GaballaGit wants to merge 5 commits into
Closed
Conversation
Collaborator
|
If you haven't already look at the cache logs, it requires a flakehub account |
Member
Author
|
bruh |
Member
Author
|
looks like its still fine, it used another way to cache. The second ci test ended with a cache hit. Also flake hub seems to have been an issue before this (ex: domain+dto for events a few days ago) |
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.
The current CI spends a lot of time setting up nix. This PR introduces cacheing for nix so that our CI time will go down dramatically.