What is a CI/CD Pipeline?
Learn what a CI/CD pipeline is — build, test, deploy stages, quality gates and triggers — with a DevOps interview question answered.
Expected Interview Answer
A CI/CD pipeline is the automated sequence of stages — checkout, build, test, and deploy — that takes a code change from commit to running in an environment, with each stage gating the next on success.
The pipeline is triggered by an event such as a push or pull request, then runs a defined series of jobs in order or in parallel. A typical pipeline checks out source, installs dependencies, compiles or bundles the app, runs automated tests and static analysis, and finally packages and deploys an artifact. Each stage acts as a quality gate — a failure in build or test halts the pipeline before a broken change reaches later stages or production. Pipelines are usually described declaratively in a YAML file stored alongside the code, so the process itself is versioned and reviewable.
- Removes manual, error-prone release steps
- Enforces quality gates before every deployment
- Gives fast, consistent feedback on every change
- Makes the release process versioned and auditable
AI Mentor Explanation
A CI/CD pipeline is like the fixed sequence a player goes through before playing a match — fitness test, nets session, selection review, then the field. Each stage is a checkout-build-test-deploy step, and failing the fitness test (a broken build) stops the player from reaching the nets at all. Passing every stage in order means only validated players reach the field, just as only a passing build reaches production. The stages always run in the same declared order, defined in the team’s written selection policy.
Step-by-Step Explanation
Step 1
Trigger
A push, pull request, or schedule starts the pipeline automatically.
Step 2
Checkout and build
The pipeline fetches source code and compiles or bundles it into an artifact.
Step 3
Test and gate
Automated tests and checks run; a failure halts the pipeline before later stages.
Step 4
Package and deploy
A passing artifact is packaged and released to the target environment.
What Interviewer Expects
- Clear ordered stages: checkout, build, test, deploy
- Understanding that each stage gates the next
- Awareness that pipelines are defined declaratively in code
- Knowing what triggers a pipeline run
Common Mistakes
- Describing the pipeline as a single undivided step
- Forgetting that a failure should halt later stages
- Confusing the pipeline definition with the CI/CD practice itself
- Not mentioning what event triggers a run
Best Answer (HR Friendly)
“A CI/CD pipeline is the automated checklist code goes through before it reaches users — building it, testing it, and releasing it, all triggered automatically whenever someone pushes a change. If any step fails, the process stops before the broken change can cause harm.”
Code Example
name: pipeline
on: [push]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm ci
- run: npm run build
test:
needs: build
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm test
deploy:
needs: test
runs-on: ubuntu-latest
steps:
- run: ./deploy.shFollow-up Questions
- What triggers a CI/CD pipeline to run?
- How do you handle a stage that fails intermittently?
- What is the difference between stages and jobs in a pipeline?
- How would you speed up a slow pipeline?
MCQ Practice
1. What happens when a stage in a CI/CD pipeline fails?
A failed stage halts the pipeline, acting as a quality gate that blocks broken code from reaching later stages.
2. Where is a CI/CD pipeline typically defined?
Pipelines are usually defined as YAML files stored in the repository, so the process itself is versioned and reviewable.
3. What commonly triggers a pipeline run?
Pipelines are typically triggered by events such as a push, pull request, or a schedule.
Flash Cards
What is a CI/CD pipeline? — The automated staged sequence taking a code change from commit to deployment.
Name the typical stages. — Checkout, build, test, package, deploy.
What happens on a failed stage? — The pipeline halts, preventing later stages from running.
Where are pipelines defined? — In a declarative config file (e.g. YAML) versioned with the source code.