Pipeline
In one line
A pipeline is an automated sequence of steps (build, test, deploy) that code passes through from commit to production.
In simple words
A pipeline is the automated flow that your code goes through from the moment a developer commits it to the moment it reaches production. It is a series of stages connected like a pipe — the output of one stage feeds into the next.
A typical pipeline has stages like: Source (trigger on commit) → Build (compile code) → Test (run automated tests) → Package (create artifact/image) → Deploy (push to environment). If any stage fails, the pipeline stops and the team is alerted.
Pipelines make deployments reliable and repeatable. Instead of a developer manually building and deploying, the pipeline does it the same way every time — no human error, no forgotten steps.
Example
pipeline:
- stage: Build
run: npm run build
- stage: Test
run: npm test
- stage: Package
run: docker build -t app:latest .
- stage: Deploy
run: kubectl apply -f k8s/A conceptual pipeline with four stages: build, test, package as Docker image, and deploy to Kubernetes.
How it works
- A trigger fires the pipeline (commit, PR, schedule, manual).
- Each stage runs in order — build, test, package, deploy.
- If a stage fails, the pipeline stops and sends an alert.
- If all stages pass, the code reaches the target environment.
Common confusions
Confused with: Workflow
The difference: A pipeline is a linear sequence of stages; a workflow can have branching, parallel paths, and complex dependencies.
Related terms
Decode error messages
Plain-English explanations of common errors — what they mean, why they happen, and how to fix them.