Infrastructure Code Continuous Delivery Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
:[[File:Infrastructure_Delivery_Pipeline.png|878px]] | :[[File:Infrastructure_Delivery_Pipeline.png|878px]] | ||
==Activities== | ==Activities== | ||
===Build=== | ===Build=== | ||
The build stage compiles application code, runs unit tests and integration tests, in as [[#Offline|offline]] and [[#Online|online]] testes, and publishes a deployable artifact in a repository. | The build stage compiles application code, runs unit tests and integration tests, in as [[#Offline|offline]] and [[#Online|online]] testes, and publishes a deployable artifact in a repository. | ||
| Line 24: | Line 24: | ||
===Apply=== | ===Apply=== | ||
===Validate=== | ===Validate=== | ||
==Stages== | ==Stages== | ||
Revision as of 00:31, 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
Activities
Build
The build stage compiles application code, runs unit tests and integration tests, in as offline and online testes, and publishes a deployable artifact in a repository.
Offline Tests
Online Tests
In a dedicated environment.
Promote
Apply
Validate
Stages
TO CONTINUE: IaC Chapter 8 Core Practice: Continuously Test and Deliver → Infrastructure Delivery Pipelines.
TO INTEGRATE:
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