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.
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.