To be honest I've always found the best approach with most of these systems is to checking your magic as shell-scripts inside your repository. Then you're much

To be honest I've always found the best approach with most of these systems is to checking your magic as shell-scripts inside your repository. Then you're much much more portable. Want to run tests? Run ".ci/tests.sh", want to generate artifacts "make", or ".ci/build.sh". All systems, be they github actions, jenkins, gitlab-runners, and everything else allow you to clone/update your repository and run something from within it. Which keeps things mostly portable. I put together a simple github action a long time ago, but now of course I realize it is overkill: https://github.com/skx/github-action-tester/ https://github.com/skx/github-action-tester/