Best practices for setting up CI tests for a Stack project?

• stack

  47 3,949 9.9 Haskell

  The Haskell Tool Stack

  

stack test tries to rebuild the whole project after I run stack build, eating into local development speed. This is an open issue. The suggested workaround of building with --test --no-run-tests still incurs noticeable build time overhead because it also rebuilds all the test suites.

• Cabal

  84 1,563 9.8 Haskell

  Official upstream development repository for Cabal and cabal-install

  

or use a cabal pre-release version that adds support for remote freeze files: https://downloads.haskell.org/~ghcup/unofficial-bindists/cabal/3.7.0.0-pre20220407/

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• wasp

  192 11,627 9.7 TypeScript

  The fastest way to develop full-stack web apps with React & Node.js.

  

You can check out current Github CI workflow here, it uses Cabal, to which we switched recently: https://github.com/wasp-lang/wasp/blob/main/.github/workflows/ci.yaml .

• hledger

  86 2,759 9.8 Haskell

  Robust, fast, intuitive plain text accounting tool with CLI, TUI and web interfaces.

I run stack-based CI tests, and they are heavier than I like, but complete in about 2m. https://github.com/simonmichael/hledger/blob/master/.github/workflows/main.yml in case it has any tips.

Suggest a related project