What Is a CI/CD Pipeline?

A CI/CD pipeline is an automated sequence of steps — building, testing, and deploying code — that runs whenever changes are pushed, replacing manual release...

Published October 9, 2026

A CI/CD pipeline is an automated series of steps that builds, tests and deploys code every time it changes. It replaces manual releases with a repeatable process.

The concept

Typical stages: checkout, install, lint, test, build, package, deploy. A failing stage stops the pipeline.

Pipelines are defined as code (YAML) in tools like GitHub Actions, GitLab CI or Jenkins.

Stages

  1. Commit triggers the pipeline
  2. Install and lint
  3. Test and build
  4. Deploy to staging, then production

Practical examples

GitHub Actions

on: { push: { branches: [main] } }
jobs:
  ci:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm ci && npm test && npm run build

Deploy job

  deploy:
    needs: ci
    steps:
      - run: ./deploy.sh

Secrets

env:
  API_KEY: ${{ secrets.API_KEY }}

Common mistakes

  • Committing secrets into the pipeline file.
  • Pipelines so slow nobody waits for them.
  • No rollback plan.

Key takeaways

  • Automate build, test, deploy.
  • Pipeline as code.
  • Keep it fast and secret-safe.

FAQ

Where do secrets go?

In the CI tool's encrypted secret store.

How long should a pipeline take?

Aim for minutes, not tens of minutes.

More General articles