If you think of a CI configuration as a shell script, then this is normal and not surprising. A CI config is just a big job that invokes a bunch of tools like

If you think of a CI configuration as a shell script, then this is normal and not surprising. A CI config is just a big job that invokes a bunch of tools like "go build" or "npm test", which is exactly what a shell script is too. I would get rid of the YAML and use shell for the whole thing :) Shell does have some problems, like needing to be more parallel, incremental, and reproducible, but the YAML-based CI systems all have those problems too. Related: http://www.oilshell.org/blog/2021/04/build-ci-comments.html#ci-services-as-a-bridge-between-shell-and-distributed-systems http://www.oilshell.org/blog/2021/04/build-ci-comments.html#... (and the entire post)