Nix based GHAs for easy reproducibility and cross compilation. #386
Conversation
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
angerman
changed the title
|
One thing, which the PR still lacks, is windows cross -> test artifacts on windows. Using upload/download artifacts. But this should give a good first impression of the actions/devx workflow. |
No more whitespace
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This reuses our haskell.nix infrastructure through the input-output-hk/devx repository to build GHAs that effectively run
(as well as JavaScript and Windows cross).
This is distinctly different from running the GHA using input-outpu-hk/actions/base + haskell, in that they use linux and macOS builder only (windows is cross compiled on linux). Re-using the same infrastructure we use to build full nix builds as well, however, building the application in a shell. Thus you effectively use nix to provision the environment, while using usual tools (cabal, ghc, ...) to actually build the software.
This also means, you can trivially debug the situation in CI, by simply sparing the same local shell on you linux (and macOS) machine. It also means we should soon be able to debug windows cross (and javascript cross) topics fairly easily.