continuous integration

Automatically building and testing every change as soon as it is pushed, so problems are caught early.

In more detail

Each change is merged often and checked by an automated pipeline, which runs the build, the linters and the tests. A failing check blocks the change before it reaches everyone else.

Examples

An Ansible pipeline typically runs ansible-playbook --syntax-check, ansible-lint and Molecule on every change.
For a design system the checks include compiling tokens, unit and accessibility tests with axe-core, and visual regression screenshots.
Commit-message rules enforced locally by a Git hook are enforced for real in CI.
gofmt -l . && go vet ./... && go test ./...
Run the Testcontainers integration suite deliberately in CI.
A CI service account reading Kubernetes secrets with curl from an outside address is worth an alert.
In Terraform: For Terraform, continuous integration runs terraform fmt -check, terraform init -backend=false, terraform validate, tests and a plan on every pull request. The plan is published for review, and apply runs only after approval from a protected branch.
In this course: CI logs should carry verbose test output so failures can be read weeks later. Tests that write into the repository or depend on a developer's machine are the ones that break there.

Related terms

Taught in

References

Certification courses