
Designing healthy and agnostic CI/CD pipelines
Rationale You want to keep your project healthy, approachable, and maintain readable CI/CD pipelines. You want to avoid strong dependencies on specific vendors, technologies, or CI runners, ensuring the flexibility to switch providers if needed. Vendor lock-in is problematic, among other reasons, because: Changes in the cost model Changes in the ToS Feature sets, and the corresponding API surface may change and go in a direction you don’t like Competitors may get better and may be re-considered, new options can appear How With a few simple precautions and sustained attention, you can achieve this:...