4 ms·
Since all CIs seem to be allowing executing shell scripts one way or another, in theory it is possible to avoid vendor lock in by coding your CI as a shell scri
by distcs 4y ago
Since all CIs seem to be allowing executing shell scripts one way or another, in theory it is possible to avoid vendor lock in by coding your CI as a shell script which is called from the CI configuration file. This way only the very minimal bootstrapping stuff remains in CI config and the rest remains in your shell scripts that you can port to any CI.
- mdaniel 4y agoI see this same sentiment comment in every one of these threads, and that reductionist view seems to ignore the things that make CI valuable: conditional stages, caching, passing artifacts from one to another, secret management, etc If the retort is "well, just implement those things in your shell scripts" then at that point one has reimplemented Earthly in shell which feels objectively worse