@alexmiller What's the status of https://github.com/clojure/build.ci/blob/master/ci_data.clj these days, now that repos use GH actions for CI?
It looks like everything runs https://github.com/clojure/build.ci/blob/master/.github/workflows/test.yml which does a Java matrix of 8, 11, 17, 21 and a Clojure matrix of 1.9.0, 1.10.3, 1.11.3?
That meshes with what I see run for core.unify which @fogus and I were discussing on Ask: 12 jobs (4 Java x 3 Clojure).
Does that mean there's:
a) no automated testing against earlier versions of Clojure
b) no testing against 1.11.4 or 1.12.0
c) no testing against a different set of JVMs
Yes
We do actually test most of the contribs in the regression before we release
My question was more: can an individual contrib lib specify a different testing matrix?
Most of the contrib actions use the same template, so that should be updated (a few are special cased copies)
(several contribs have deps.edn testing setups for multi-version testing, via a script or something, but that's for dev/test locally, not CI)
It’s not parameterized right now (wasn’t easy to do that in gh actions at the time), so we just copied the template and modified for the few special ones
The thought was that maybe I would ultimately go back to using something ci_data to gen the contrib workflow files eventually but didn’t get around to that
A few contribs were being tested against 1.8 and earlier before -- and that's reflected in their deps.edn etc -- but I had forgotten (or didn't know) that stopped with the switch to GH actions... Probably just a matter of cleaning up the dev/test deps at this point.
Should someone update that clojure-version line in those workflows?
Oh, you just did! Thank you!
I updated the template to add 1.11.4 and 1.12.0
Yeah it was a while that I stopped testing anything older