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)

A victim of your own success

Humans are very fickle beings. As businesses are mostly staffed by humans, they are also fickle. A moment of success soon passes and fades into the collective memory, and problems that were not problems a few weeks/months ago start to become the talk of the town, boardroom, water cooler, or washroom. Another problem with success is that this becomes the baseline, which means that even the smallest of problems can start to become a major issue relatively quickly. These problems can be relatively simple things, such as:

As adoption matures, relatively small issues can become the new problems

In the space of a few months, the vast majority of the team members originally working within the constraints of big release cycleswhich took many weeks or months to pull together, test, and push into the production environmenthave all but forgotten...