CI/CD Pipeline

Noun · Open Source

Definitions

  1. The automated sequence of steps that code goes through from commit to production — build, test, security scan, staging deployment, and production release. A well-configured pipeline catches bugs before humans do. A poorly configured one just gives you green checkmarks while production burns.

    In plain English: The automated assembly line that takes your code from the moment you save it all the way to running in production — building it, testing it, and deploying it without manual steps.

  2. A mature pipeline typically includes: lint/format check, unit tests, integration tests, security scanning (SAST/DAST), container build, staging deployment, smoke tests, and production deployment with automatic rollback on failure. Building this incrementally is key — don't try to boil the ocean.

    Example: 'Our pipeline runs 2,400 tests in 8 minutes, scans for vulnerabilities, deploys to staging, runs E2E tests, and auto-deploys to production. Took us two years to get here.'

    Source: maturity stages

Etymology

1991
Grady Booch coins 'continuous integration' in his book on object-oriented design
2001
CruiseControl (and later Jenkins in 2011) automate the build-test cycle, making CI a standard practice
2013
Docker containers revolutionize CD pipelines, making reproducible deployments possible across environments
2018
GitHub Actions, GitLab CI, and cloud-native pipelines make CI/CD accessible to every project, not just enterprises

Related Terms