Book Image

Continuous Delivery and DevOps ??? A Quickstart Guide - Third Edition

By : Paul Swartout
Book Image

Continuous Delivery and DevOps ??? A Quickstart Guide - Third Edition

By: Paul Swartout

Overview of this book

Over the past few years, Continuous Delivery (CD) and DevOps have been in the spotlight in tech media, at conferences, and in boardrooms alike. Many articles and books have been written covering the technical aspects of CD and DevOps, yet the vast majority of the industry doesn’t fully understand what they actually are and how, if adopted correctly they can help organizations drastically change the way they deliver value. This book will help you figure out how CD and DevOps can help you to optimize, streamline, and improve the way you work to consistently deliver quality software. In this edition, you’ll be introduced to modern tools, techniques, and examples to help you understand what the adoption of CD and DevOps entails. It provides clear and concise insights in to what CD and DevOps are all about, how to go about both preparing for and adopting them, and what quantifiable value they bring. You will be guided through the various stages of adoption, the impact they will have on your business and those working within it, how to overcome common problems, and what to do once CD and DevOps have become truly embedded. Included within this book are some real-world examples, tricks, and tips that will help ease the adoption process and allow you to fully utilize the power of CD and DevOps
Table of Contents (13 chapters)

Measuring effective engineering best practices

This is quite a weird concept to get your head around: How can you measure effective engineering, and more than that, how can you measure best practices? There's another often-asked question: what has this got to do with DevOps or CD? We'll look at the former in a moment, but now let's focus on the latter.

Let's take two scenarios:

  • Your current software-engineering process is very waterfall and you have a vast amount of manual testing to validate your code just before it gets shippedwhich happens every 3-6 monthsand build in a buffer for bug fixing
  • Your current software-engineering process is pretty agile and follows (mostly) industry best practices, however as there is plenty of time between releases you can sometimes let technical debt slip (including test automation) as there will be time to...