yes, I would prefer it. CircleCI is another option but I’m not familiar with them and they could stop/limit supporting free OSS plans like travis did.

another option is to run the tests in canary’s GH Action - currently canary itself runs as GH Action (it used to run on Travis)

original idea was to trigger test builds on projects “remotely” via API and wait for results, so that project maintainers maintain their test systems, but @U04VDQDDY ended up wrapping most projects in chkup and maintaining them himself

canary can run shell scripts instead of triggering builds via APIs, but then we would have to maintain the scripts running the tests for such projects

is it possible to run other repos tests? doesn't that require coordination of some kind?

people had to submit their travis tokens to canary, so that canary can trigger their builds remotely

https://github.com/cljs-oss/canary/tree/master#how-can-i-trigger-travis-build-of-my-project

and also people had to use CANARY_CLOJURESCRIPT_VERSION in their deps, to consume tested cljs compiler: https://github.com/binaryage/cljs-devtools/commit/45c1df1e0de53c9d320963b296bd7a741056599c

what I mean is will switching this to GH actions also require collecting tokens?

yes, if we wanted to trigger builds/tests on other people’s repos travis allowed storing encrypted tokens, so that wasn’t really big issue

not sure about GH Actions, but we could do it more dirty way and simply maintain the test scripts ourselves and run the tests inside canary’s GH Action

it is explained here: https://github.com/cljs-oss/canary/tree/master#can-you-give-me-more-details-on-how-can-i-can-participate-with-my-project

you can write a shell script, which can do whatever it wants to test particular project

this script runs inside canary’s GH action (actually inside docker there)

@darwin isn't another option to just clone the project, use clj to set the version and avoid all the token stuff?

then we maintain nothing other than the GH workflow entries

ah, I see, you mean that we would create multiple GH workflow entries under the canary repo and trigger them from canary runner with a single token (our token)

that is also an option

that “shell script” option I was talking about is more direct, canary runner is running in GH workflow and it would run the tests directly in-process, by launching some shell scripts which would clone repos and run tests the way they are meant to be run from command-line

hrm, but there's a benefit w/ workflow per project since you get UI overview of the results

or maybe you mean to ditch canary altogether and just use github workflows to do multi-test

maybe it is possible, I’m not that familiar with GH Actions

canary was designed before GH Actions were announced

I just mean that canary could basically just be a bunch of workflows

yes, I see

there would be just one special at the beginning which would compile the compiler for subsequent workflows to use it

I'm relatively familiar and this will be mostly copy-pasta - will try to find some time to think about it

might just make canary2 or something in cljs-oss org

ok, give it a shot, I think that would be great

👍:skin-tone-4:

FWIW, I test tagged releases of known projects that use rewrite-clj against rewrite-clj master. Currently all runs sequentially, but works for my purposes https://github.com/clj-commons/rewrite-clj/blob/main/script/test_libs.clj