Chapter 3. The Mindset Shift
As I mentioned in Chapter 1, initiating continuous deployment requires only a small change for a team that already has a good continuous delivery pipeline. Usually, this change amounts to one line: removing manual approval from production deployments.
The real challenge with this practice does not lie in its implementation, but in the fact that as soon as it is implemented, developers have to start thinking differently about how they write code. In particular, they need to author every commit while keeping in mind their immediate proximity to production.
Planning development with immediate production deployments in mind is a big difference in workflow, and one that might take some time getting used to. This has certainly been my experience, and for a time it has caused a sense of uncertainty in my teams when touching our codebase. Back then, I wished there were more resources to explain how to adapt our day-to-day work to this paradigm, which is also one of the reasons I started to write about it. Although it seemed a bit intimidating at the beginning and we made some mistakes along the way, over time we noticed how our gradual shift in mindset made a positive impact on the speed and quality of our work.
Therefore, the aim of this chapter is to collect the main “gotchas” of continuous deployment to help you fast-track the same learning process that we had to figure out from scratch and harvest its benefits earlier. I hope this will help reduce the ...
Get Continuous Deployment now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
