pipeline

An automated sequence of steps, such as build, test, scan and publish, that runs on every change.

In more detail

Pipelines run automatically, usually in a CI service, so every change gets the same checks. Anything a pipeline runs must be written in files with versions pinned, because nobody is there to type commands.

Examples

A pipeline can act as the Ansible control node, linting and testing roles and then applying playbooks.
The course pipeline runs a lint gate, then unit, integration and end-to-end tests, then builds one artifact that later stages promote. A pipeline owns validation and provenance; a GitOps controller owns convergence.
cd ci && bash pipeline.sh
A token pipeline compiles design tokens for every platform; a CI pipeline runs accessibility and visual tests before a change can merge.
In Terraform: A Terraform pipeline typically formats, initialises, validates, tests, plans, checks policy and, after approval, applies. It must never stop to ask a question, so it passes -input=false and applies saved plans.
In this course: A quality gate is expressed as pipeline jobs: lint, types, unit tests and a focused integration suite, each with a clear failure message. In continuous integration the pipeline runs on every push and pull request.

Related terms

Taught in

References

Certification courses