Infrastructure as Code, 3rd Edition

Chapter 16. Infrastructure Delivery Pipelines

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles. This will be the 16th chapter of the final book. Please note that the GitHub repo will be made active later on. If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

TODO

Add examples. Pipelines may be a bit tougher to grasp, especially because not everyone does them the same way, and my explanations are pretty abstract.

In the previous chapter I described how continuously testing infrastructure changes during development help to make releasing new and changed systems easy and reliable. In this chapter I’ll discuss the design and implementation of automated pipelines to manage the infrastructure delivery lifecycle.

Infrastructure Delivery Pipelines

A Continuous Delivery pipeline is an automated implementation of a delivery workflow.¹

Figure 16-1 is an example of a simple pipeline.

Figure 16-1. Example of basic delivery pipeline stages

A developer commits code to push it into the build stage of the pipeline. Different pipelines will have different ...