Infrastructure Code Continuous Delivery Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 11: Line 11:


=<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=
:[[File:Infrastructure_Delivery_Pipeline.png]]
:[[File:Infrastructure_Delivery_Pipeline.png|878px]]
==Activities==
==Activities==
A infrastructure delivery pipeline implies multiple types of activities, grouped in stages:
A infrastructure delivery pipeline implies multiple types of activities, grouped in 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

Infrastructure Delivery Pipeline.png

Activities

A infrastructure delivery pipeline implies multiple types of activities, grouped in stages:

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

Tools