Continuous Deployment Requires Process and Culture Change
September 8, 2015 | Author: Gabriel Schenker, Principal Software Architect
The idea of Continuous Deployment has become a hot topic in the software engineering industry. Clear Measure Principal Software Architect, Gabriel Schenker, recently wrote a blog post about the changes that go into place when moving to a Continuous Deployment process.
These days everybody wants to try new ideas as quickly as possible in the market. We want to see whether or not our customers like a new feature. If yes then we want to work on the feature and improve it and if not then we want to fail fast and learn fast from the mistake and correct fast.
To be able to do this a company producing mission critical software can embrace continuous deployment (CD). CD is not a tool nor a simple process, it is a whole pipeline of processes and associated culture changes in the company. CD in a nutshell manifests itself in such a way that if a developer finishes coding a new feature and pushes this feature to a central code repository then a process starts whose end result is that the code containing the new feature is in production and the feature is thus available to the consumers. All this happens fully automated and without any human intervention. This sounds scary, doesn’t it? Yes and no… but let’s look into more details what exactly CD implies.
Use the following link to read the full post on Continuous Deployment:
The post Continuous Deployment Requires Change in Process and Culture appeared first on Clear Measure.