Skip to main content

Topic

CI/CD & Delivery

A pipeline is the path a change takes from commit to production. Its value is not automation for its own sake: it is that every change travels the same path, so a failure is a signal about the change rather than about who deployed it.

The pipelines worth having are fast enough that nobody avoids them, and honest enough that a green run genuinely means the change is safe. Everything else — caching, parallel jobs, environment promotion — serves those two properties.

Articles
3
Answered questions
2