Infrastructure Code Continuous Delivery Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
=Overview= | =Overview= | ||
The [[#Pipeline|delivery pipeline]] metaphor describes how a change in the infrastructure code progresses from the person that makes the change all the way to production. | |||
<font color=darkkhaki>Reconcile with [[Continuous_Delivery#Overview|Continuous Delivery]]</font>. | <font color=darkkhaki>Reconcile with [[Continuous_Delivery#Overview|Continuous Delivery]]</font>. | ||
=<span id='Pipeline'></span><span id='Infrastructure_Delivery_Pipelines'></span>Infrastructure Delivery Pipeline= | =<span id='Pipeline'></span><span id='Infrastructure_Delivery_Pipelines'></span>Infrastructure Delivery Pipeline= | ||
Revision as of 00:10, 23 January 2022
External
Internal
Overview
The delivery pipeline metaphor describes how a change in the infrastructure code progresses from the person that makes the change all the way to production.
Reconcile with Continuous Delivery.
Infrastructure Delivery Pipeline
TO CONTINUE: IaC Chapter 8 Core Practice: Continuously Test and Deliver → Infrastructure Delivery Pipelines.
TO INTEGRATE:
A typical pipeline includes stages for testing (offline, test double, online) in dedicated environments and production deployment.
Stages:
1. Build Stage. The build stage compiles application code, runs unit tests and integration tests and publishes a deployable artifact in a repository.
2. Offline Infrastructure Tests
3. Online infrastructure Tests
Organizatorium
- Modeling Deployment Pipelines: Build Propagation using Fan-in/Fan-out https://www.gocd.org/2017/04/17/build-propagation-using-fan-in-fan-out.html