6 Best Practices for Continuous Delivery Pipelines

Derik Evangelista and I talked about pipelines’ best practices during the Cloud Foundry summit EU 2018 in Basel (CH). For instance, the practices are:

  1. Changes should propagated through the pipeline immediately
  2. Deploy into a production-like environment
  3. Stop the pipeline on any failures
  4. Only build binaries once
  5. Run smoke tests in all your deployments
  6. Deploy the same way to every environment

The best practices above are the result of years of observations from engineers in the field, trying to solve issues that frequently arise during the software releasing process.

Watch the talk bellow if you are interested in why you should apply these practices and how to do it. If you want to go deeper into this topic, I recommend the Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation book by Jez Humble and David Farley.

One thought on “6 Best Practices for Continuous Delivery Pipelines

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.