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

• stack

  18 3,779 7.5 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

  32 1,417 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/

• SonarLint

  www.sonarlint.org

  sponsored

  Clean code begins in your IDE with SonarLint. Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.

  

• wasp

  22 1,899 8.9 Haskell

  A programming language that understands what a web app is.

  

  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

  32 2,166 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