What is CI/CD?
CI/CD is the habit of automatically testing every code change and, once it passes, deploying it without manual steps.
Drafted with AI from official documentation. Scripts were run in a test environment and repository links verified. Awaiting a human check. Did it work for you? Last edited Outdated?
CI/CD stands for continuous integration and continuous delivery (or deployment). CI means that every push to the repository automatically builds the project and runs the tests, so broken code is caught in minutes. CD means that code which passes is packaged and shipped to a server automatically. It is a factory conveyor belt with quality checks at each station instead of a once a year grand release.
GitHub Actions, GitLab CI, Jenkins and Tekton are the usual tools; the pipeline is described in a YAML file in the repository. A typical pipeline lints, tests, builds a container image, pushes it to a registry and tells Kubernetes or a server to update. Green ticks on pull requests come from CI.
on: [push]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: python -m pytestSee also: What is a pull request? and What is a container?
Did this work for you?
No votes yet. Be the first.
If it did not work, the report form below tells the editors what went wrong.
See also
- 0378 Continuous integration explained What continuous integration means, why small frequent merges plus an automated build on every change prevent integration pain, what a good pipeline… Beginner · Explains an idea · Any system Article Pipelines, runners & hooks 15 Oct 2026
- 0379 Your first GitHub Actions workflow: run tests on every push Build a working GitHub Actions pipeline from nothing: a small Python project with a test, a workflow file that runs pytest on… Beginner · Guided project · Any system Article GitHub Actions · Pipelines, runners & hooks 15 Oct 2026
- 0381 pre-commit hooks: catch mistakes before they are committed Install the pre-commit framework, configure hooks for whitespace, YAML and JSON syntax, large files, leaked private keys, Python linting and shellcheck, run… Beginner · Step by step · Linux, macOS, Windows Article Pipelines, runners & hooks · Setup 15 Oct 2026
- 0454 Scan your own code and containers in CI: Gitleaks, Semgrep and Trivy Set up a GitHub Actions workflow that runs Gitleaks, Semgrep and Trivy on every push of your own project, learn what each… Intermediate · Step by step · Any system Article Pipelines, runners & hooks · Security testing & CTF 15 Oct 2026
Repos in the wild
- pre-commit: a framework for managing multi-language Git hooks pre-commit/pre-commit The pre-commit repository: the tool that installs, isolates and runs Git hooks declared in a YAML file, with hooks written in Python, Node, Go, Rust, Ruby, Docker and more, pinned to exact versions. GitHub
- Woodpecker CI: a lightweight, self-hosted CI engine with container-based pipelines woodpecker-ci/woodpecker The Woodpecker CI repository: a community fork of Drone that runs every pipeline step in its own container, connects to GitHub, Gitea, Forgejo, GitLab and Bitbucket, and runs on a single small server. GitHub
- Gitleaks: find secrets that were committed to a Git repository gitleaks/gitleaks Gitleaks scans Git history, working trees and arbitrary files for passwords, API keys, tokens and private keys using a library of patterns, and is usually run as a pre-commit hook and in CI. GitHub
- Semgrep: static analysis with rules you can read semgrep/semgrep Semgrep is a fast static analysis tool whose rules look like the code they match, with a community registry of thousands of rules for finding bug patterns and insecure code across more than thirty languages. GitHub
History
Every saved edit is kept. The plot on the sleeve draws one line per edit. Open any edit to see exactly what changed.
- Dominik +894 chars