CD – Post Deployment

Code Review      Code Versioning     Communication     Deployment Preparation   Testing       References

Continuous Deployment – Post Deployment Practices

In continuous deployment there are different practices that adoptees perform after they deploy their software changes in production. These practices include monitoring and analysis, use of feature flag, and dark launches. The objective of these practices is to get feedback and take necessary actions relevant to the deployment as soon as possible. Not all of the 20 adoptees have reported to perform these practices.

  • By monitoring and analysis, we mean once software changes are deployed if tools are used to monitor performance, errors, and analyzed in order to predict and correct errors. Along with in-house tools other tools such as Logster, and statsD are used. Here we present how many of the 20 adoptees perform monitoring and analysis as part of their deployment process.
  • Feature flags are also known as switches or feature toggles which are used to activate or deactivate specific portions of the software changes. Dark launches is another practice where software changes are tested without changing the user interface. In this way the end-user of the product will not be aware of software changes are made. The number of companies who use feature flags and dark launches are presented as following.
  • Shepherding changes is the practice of developers making software changes and being responsible for those software changes throughout the whole deployment process. The main motto of shepherding changes is getting involved in all the steps of the continuous deployment which includes writing software changes, running different tests on the software, deploying software changes into production, and fix problems that arise after deployment. To implement the practice of shepherding changes adoptees use different techniques. For example, Facebook arranges boot camps for incoming developers so that they get habituated to Facebook’s deployment and development practices.

(*) Practice Unknown in the bar/pie chart represents the number of companies who have not reported their related practices.

Links to other practices and references:

Code Review      Code Versioning     Communication     Deployment Preparation   Testing       References

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>