Skip to content
BENIBIX Learn

CI/CD Pipeline

Development☁️ DevOps & CloudCI/CD

Also known as CI/CD, Pipeline, Deployment Pipeline, Build Pipeline

The steps a machine runs on each change, from commit to live.

Think of it like

Think of it like a car factory line. Each station does one job, and a car that fails a check is pulled off.

Example

Emma's pipeline has five stages. A change takes 12 minutes from push to production, and last week it stopped two bad changes at the test stage.

Why it matters

Every release follows the same safe steps. Nothing gets skipped when people are tired or rushed.

Definition

A CI/CD pipeline is the list of steps a machine runs on each change on its way to users. A common order is build, test, scan, deploy to staging, then deploy to production. Each step must pass before the next one starts. If one fails, the pipeline stops and tells the team. The steps are written down in a file kept with the code.

Common mistake

Letting the pipeline grow slow, like an hour per run. People then batch changes up, and the point is lost.

Key takeaways

  1. 1
    Steps in order. Build, test, deploy.
  2. 2
    Stops on failure. Bad changes go no further.
  3. 3
    Written as code. Kept with the app.