Home › Key concepts › CI/CD

Key concept · Crawl (beginner) · the same on every platform

CI/CD

Every change is built, tested and deployed by a pipeline, not by hand.

What it is

Continuous integration runs the tests on every change. Continuous delivery packages the change and deploys it to an environment automatically, with approvals where needed.

Why it matters

Manual deploys are slow and error-prone. A pipeline does it the same way every time.

An example

Merging a pull request runs tests, builds a container and deploys it to staging within ten minutes.

The common mistake

A 'deploy guide' document with 23 manual steps.

Where you meet it on each platform

The idea stays the same; only the product name changes.

JobAWSAzureGoogle CloudDatabricksOpen source
CI/CDevery change is tested and shipped by a pipeline, not by handGitHub Actions + CodeDeployGitHub Actions or Azure PipelinesGitHub Actions + Cloud BuildGitHub Actions + bundlesGitHub Actions

Related ideas

Where it shows up

Part of the Crawl level on these paths: ML Engineering (production ml) · Software Engineering (working together).