DEV Community

Discussion on: DevOps 101: CI/CD

Collapse
abdelrahmanahmed profile image
Wahdan

Even in most trusted well tested systems, pushing to production directly is not recommended, you can setup a mix between continuous delivery and continuous deployment if you have multiple environments.

Collapse
katcosgrove profile image
Kat Cosgrove Author

You've misunderstood me. I don't think you should push straight to production, and nowhere in this article did I say that anyone should. What I said is that a sufficiently robust CI/CD system automates work that used to be manual, which can easily include promotion of a build from a dev or testing environment to the production environment. I just don’t believe that it’s always necessary to have a human pushing the Deploy button for prod. That’s a security blanket, not a real quality gate. Investing heavily in those automated quality gates builds trust that allows you to eventually remove human intervention without sacrificing confidence in quality.

Anyway, this is a beginner-friendly explanation of what CI/CD is, not a best practices article for DevOps at enterprise scale. :)