CI/CD Pipeline Stages
Typical stages in a continuous integration and delivery pipeline.
The stages a change passes through from source control to production and back as monitoring feedback: source, build, test, deploy, operate and monitor, plus planning, review, security scanning, packaging, release and rollback stages that mature pipelines add.
Use it when
- You are designing or documenting a delivery pipeline and need consistent stage names.
- You are checking a pipeline for missing safety stages.
Watch out for
- Stage names and boundaries differ between tools; a CI server may merge several stages into one job.
- More stages are not better by themselves; each should produce a signal someone acts on.
The data
12 rows
| Stage | Description |
|---|---|
| Source | Trigger pipeline on code commit or pull request. |
| Build | Compile, package, and create artifacts. |
| Test | Run unit, integration, and security tests. |
| Deploy | Release artifacts to staging or production. |
| Operate | Run the application in the target environment. |
| Monitor | Collect metrics, logs, and alerts for feedback. |
| Plan | Capture and prioritize the work that will become changes, linking tickets to code. |
| Code Review | Peers inspect a change before merge to catch defects and share knowledge. |
| Static Analysis and Security Scan | Automated linters, static application security testing and dependency checks run on every change. |
| Package | Produce a versioned, immutable artifact such as a container image or package and store it in a registry. |
| Release | Promote a tested artifact to an environment, often gradually through canary or blue-green strategies. |
| Rollback | Return to the last known good version quickly when a release misbehaves. |
Fields
The shape of this dataset, read from the data itself: every column, its type and a real value. Agents can use this to plan a query without fetching the whole document.
| Section | Field | Type | Example |
|---|---|---|---|
| data | stage | string | Source |
| data | description | string | Trigger pipeline on code commit or pull request. |
Fetch the same bytes
The static files contain the same reference rows as the API, with no API rate limit. Live metadata, such as view counts, may differ. Use the API for content negotiation; use the static files for a cacheable snapshot.
curl "https://yjtoon.yunusemrevurgun.com/api/dataset/cicd-pipeline-stages?format=toon"
const res = await fetch( "https://yjtoon.yunusemrevurgun.com/static-data/dataset/cicd-pipeline-stages.toon" ); const toon = await res.text();
Rate limit: 120 requests per minute per IP, no key and no signup. API reference →