4 ms·
DevOps is about removing a secondary team that you throw something over the wall to for deployment. Instead the build pipeline (be it Circle, GitabCI, Jenk, Go,
by rhacker 8y ago
DevOps is about removing a secondary team that you throw something over the wall to for deployment. Instead the build pipeline (be it Circle, GitabCI, Jenk, Go, etc...) can control ALL environments and things have been optimized, in such a way, that a single click updates an environment. (including prod). The pipeline "code" and all its related scripts are the actual devops work products. They CAN be done by a single team that supports multiple other teams, but truthfully it should be a shared responsibility. Perhaps one team provides base scripts and answers the questions about where logs and monitoring data go (and of course those questions are answered with scripts essentially). So "ops" can still exist if your organization is large enough, but I definitely say there's no "thing" you throw over the wall anymore.
- nickthemagicman 8y agoSo it's a secondary team to replace the secondary team.
- camelNotation 8y agoAlways. The question with any form of process optimization is how much smaller does the human presence need to be? The idea that we would replace people entirely is a sales pitch.
- chupasaurus 8y agoThe difference is an automation of a contract to make a new release in production: the process of delivering a new code should make all the necessary checks such as CI, regression tests, monitoring endpoints and so on up to deployment itself, in a reproducible manner.