Publish to a Binary Cache about crate2nix HOT 5 CLOSED

@vbrandl Thank you for the suggestion! My travis setup was horrible. I try this out currently....

from crate2nix.

Thank you for the suggestion. The github action results in a build now. But the caching doesn't seem to work since it is still rebuilding everything from scratch. If you have an idea on how to change that, please let me know!

from crate2nix.

I'm not sure (never used the action before, I just thought, it might work)

Maybe you need to build default.nix instead of tests.nix for the caching to work and run the tests in a separate step? Just spitballing here...

from crate2nix.

I think one of the problems with the current cachix approach in the GitHub action is that it isn't caching intermediate results aka all the dependencies of crate2nix.

Ideally we would be able to use the post-build-hook together with cachix. That would ensure all the build results get uploaded to the binary cache.

I briefly looked into the cachix github action and there seems to be a few requests for ways to customize the behavior.

from crate2nix.

I implemented to improvements so I'll close it now:

• In run_tests.sh, I also include a cachix push on my machine so that everything that I push to the github repo is usually prebuilt.
• I updated the version of the cachix hook so that this uses a post-build-hook now.

from crate2nix.