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

• stack

  10 3,913 9.6 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

  11 1,532 9.4 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/

• Onboard AI

  getonboard.dev

  sponsored

  Learn any GitHub repo in 59 seconds. Onboard AI learns any GitHub repo in minutes and lets you chat with it to locate functionality, understand different parts, and generate new code. Use it for free at www.getonboard.dev.

  

• wasp

  114 8,395 8.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

  22 2,584 9.6 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