Infrastructure Code Continuous Delivery Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
* [[Continuous_Delivery#Continuous_Delivery_for_Infrastructure_Code|Continuous Delivery]] | * [[Continuous_Delivery#Continuous_Delivery_for_Infrastructure_Code|Continuous Delivery]] | ||
* [[Infrastructure_as_Code_Concepts#Infrastructure_Code_Continuous_Delivery|Infrastructure as Code Concepts]] | * [[Infrastructure_as_Code_Concepts#Infrastructure_Code_Continuous_Delivery|Infrastructure as Code Concepts]] | ||
* [[Infrastructure_Code_Testing_Concepts#Overview|Infrastructure Code Testing]] | |||
=Overview= | =Overview= | ||
=<span id='Infrastructure Delivery Pipelines'></span>Infrastructure Delivery Pipeline= | =<span id='Infrastructure Delivery Pipelines'></span>Infrastructure Delivery Pipeline= | ||
Revision as of 00:15, 3 January 2022
External
Internal
Overview
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