Infrastructure Code Continuous Delivery Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 15: Line 15:
===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.
===<span id='Offline'></span>Offline Tests===
====<span id='Offline'></span>Offline Tests====
 
===<span id='Online'></span>Online Tests===
===<span id='Online'></span>Online Tests===
In a dedicated environment.  
In a dedicated environment.  

Revision as of 00:15, 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

Stages

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

TO CONTINUE: IaC Chapter 8 Core Practice: Continuously Test and Deliver → Infrastructure Delivery Pipelines.

TO INTEGRATE:

Organizatorium

Tools