A more native GitHub Actions workflow would be nice

[bensheldon]

The GitHub Actions workflow for testing Trilogy would likely be faster and more maintainable if it used more GitHub Actions-native functionality. This would mean for the workflow to set up different services through GitHub Actions and use ruby/setup-ruby to run tests within a matrix.

The current GitHub Actions workflow uses Docker in the script/cibuild to build and run docker containers within the CI environment, which is slow and not the best use of GitHub Actions:

trilogy/script/cibuild

Lines 53 to 57 in b11647a

	docker-compose rm -s -f -v
	output_fold "Pull cache image..." docker-compose pull app || true
	output_fold "Bootstrapping container..." docker-compose build
	output_fold "Running tests..." docker-compose run --rm app
	output_fold "Pushing cache image..." docker-compose push app || true # Don't fail if push fails

[ngan]

@bensheldon @composerinteralia Is there a specific reason we're testing trilogy specifically on debian? Is ubuntu good enough?

And is there a reason for this specific permutation?

trilogy/.github/workflows/ci.yml

Lines 22 to 24 in 6ed9857

	- mysql: "5.7"
	distribution: "debian:buster"
	ruby: "2.7.8"

[bensheldon]

I think that is trying to bracket with the oldest supported versions. I do think there may be some applications still using debian:buster, so unless it's a pain to keep that, I think we should keep it another year or 2 (or till we do feel pain, because I imagine coming back to this issue 4 years from now 👋)