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

1. stack

   1 50 4,012 9.7 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.

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. Cabal

   2 84 1,677 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/

4. wasp

   3 230 17,137 9.6 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 .

5. hledger

   4 89 3,298 9.9 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