4 ms·
This is the way. It also lets you pretty much seamlessly switch CI tools at any time.
by dinkleberg 3y ago
This is the way. It also lets you pretty much seamlessly switch CI tools at any time.
- jahnu 3y agoI third this opinion: another reason it’s important is it allows you to do your build in an emergency when CI is down for whatever reason. CI automation is for me the thing that replaces me running scripts one by one (and reporting/deploying results) It is not the thing that does the building/testing/deploying. That’s the scripts that are hopefully written in a debuggable, portable, language.
- simonw 3y agoThis is a really good point. Most of my deploys go via GitHub Actions these days and it's not easy for me to deploy manually should I need to when Actions is unavailable - I should fix that!
- jahnu 3y agoLike aviation, every regulation/rule is written in blood ;)
- leetrout 3y agoThis is why the three of us should record a podcast episode talking about this in the context of the points made in the Ironies of Automation https://en.wikipedia.org/wiki/Ironies_of_Automation https://en.wikipedia.org/wiki/Ironies_of_Automation
- jamesfinlayson 3y agoAgreed - I had to switch from TeamCity to GitLab earlier this year and I was very glad that all of pipelines were single-line calls to shell scripts.
- jasonm23 3y agoIndeed, to rely on third party actions in a closed runner ecosystem, is simply unwise.