Clojurians Log v2

{:paths ["src"]
 :deps {org.clojure/clojure {:mvn/version "1.11.1"}}
 :aliases
 {:dev {:extra-paths ["dev" "test" "dev-resources"]
        :extra-deps {lambdaisland/kaocha {:mvn/version "1.87.1366"}}}
  :test {:exec-fn kaocha.runner/exec-fn
         :exec-args {}}}}

Works for me

Thank you. What I really meant was a https://clojure.org/guides/tools_build integration

Ah, sorry, I misread 🙈

nb, appreciate the intent!

what would that integration look like? what are you hoping to accomplish?

I'm not entirely sure to be honest. With tools like tools.build, kaocha and babashka available, I'm trying to put together tooling around a project that makes it convenient to run and reproduce parts of a build/release pipeline both on a dev machine and in ci (gh actions/jenkins)

And so I'm looking around for examples

well, if you're merely looking to use something like clojure -T:build test, then you could rely on kaocha.repl and pass in any args

in my limited experience, there's not much difference between using a function in build.clj and just another alias in deps.edn: clojure -M:test:kaocha

yeah probably

perhaps build.clj is more focused on artifact creation ?

kaocha.repl has its drawbacks, one is that it doesn't support all plugins (cloverage for example)

At my job, we have a bin/ folder and fill it with bash scripts, so you just type bin/test or bin/build, and it calls the longer command

I started using bb tasks for that actually

and now trying to figure out how to 'front-end' all the commands - should CI invoke bb commands, should it invoke tools.build multiple times, or should is start a tools.build process that itself defines the stages of a pipeline etc

I use babaska tasks to have a one true way to run all the useful commands

I think CI can just invite BB tasks, don't see a problem with that