Infrastructure Code Continuous Delivery Concepts: Difference between revisions
| Line 14: | Line 14: | ||
:[[File:Infrastructure_Delivery_Pipeline.png|878px]] | :[[File:Infrastructure_Delivery_Pipeline.png|878px]] | ||
==<span id='Activity'></span>Activities== | ==<span id='Activity'></span>Activities== | ||
===Build=== | ===Build=== | ||
The build stage compiles application code | The build stage compiles application code and makes the code available for use for other stages. Building is usually done once in a pipeline, every time the source code changes. As result, artifacts may be published in a repository. | ||
===Promote=== | ===Promote=== | ||
Promotion means moving code between delivery [[#Stage|stages]]. | |||
===Apply=== | ===Apply=== | ||
Infrastructure code tools are executed and infrastructure resources are created based on the code. The infrastructure resources are created in different environments, corresponding to the pipeline stage the activity belongs to: stage testing, integration, production. | |||
===Validate=== | ===Validate=== | ||
Revision as of 00:37, 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
A infrastructure delivery pipeline consists in multiple types of activities, grouped in stages:
Activities
Build
The build stage compiles application code and makes the code available for use for other stages. Building is usually done once in a pipeline, every time the source code changes. As result, artifacts may be published in a repository.
Promote
Promotion means moving code between delivery stages.
Apply
Infrastructure code tools are executed and infrastructure resources are created based on the code. The infrastructure resources are created in different environments, corresponding to the pipeline stage the activity belongs to: stage testing, integration, production.
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