{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreignlrqeplyonncxa2sbycz4uilb2cptho2hd36doh2bk7xpzjjo4i",
    "uri": "at://did:plc:5sgu76a53rz3n6unbykmovqy/app.bsky.feed.post/3mlofzhtqkdx2"
  },
  "description": "A pipeline is the automated sequence of stages a code change passes through on its way from a developer's commit to production. Modern CI/CD pipelines codify build, test, security scan, package, and deploy steps so every change moves through the same checks in the same order.\n\n\nTypical stages\n\n 1. Source. Triggered by a commit, tag, or pull request from the version control system.\n 2. Build. Compile, transpile, bundle, or otherwise produce artifacts.\n 3. Test. Unit tests, integration tests, cont",
  "path": "/engineering-glossary/pipeline-cicd-stages/",
  "publishedAt": "2026-05-12T18:25:42.000Z",
  "site": "https://sahilkapoor.com",
  "tags": [
    "CI/CD",
    "GitOps",
    "ArgoCD",
    "Blue-Green Deployment",
    "Canary Deployment",
    "Feature Flag"
  ],
  "textContent": "**A pipeline** is the automated sequence of stages a code change passes through on its way from a developer's commit to production. Modern CI/CD pipelines codify build, test, security scan, package, and deploy steps so every change moves through the same checks in the same order.\n\n## Typical stages\n\n  1. **Source.** Triggered by a commit, tag, or pull request from the version control system.\n  2. **Build.** Compile, transpile, bundle, or otherwise produce artifacts.\n  3. **Test.** Unit tests, integration tests, contract tests; ideally parallelised.\n  4. **Static analysis.** Linters, type checkers, SAST, license scanning, secret detection.\n  5. **Package.** Container images, language packages, or platform-native artifacts pushed to a registry.\n  6. **Deploy.** Apply to staging, run end-to-end tests, then promote to production.\n  7. **Post-deploy.** Smoke tests, synthetic checks, observability hooks.\n\n\n\n## Design considerations\n\n  * **Parallelism.** Run independent stages in parallel to shrink wall-clock time.\n  * **Caching.** Cache dependencies, layers, and test artifacts between runs.\n  * **Selective execution.** Run only what changed (monorepo affected detection).\n  * **Approvals.** Manual gates before production deploys for regulated or high-impact services.\n  * **Reproducibility.** Pipelines as code (YAML in the repo) so the same change yields the same run.\n\n\n\n## Common pipeline platforms\n\n  * GitHub Actions, GitLab CI, CircleCI, Buildkite, Jenkins, Drone, Tekton, Argo Workflows, AWS CodePipeline, Google Cloud Build\n\n\n\n🔗\n\n**Related Terms**\nCI/CD, GitOps, ArgoCD, Blue-Green Deployment, Canary Deployment, Feature Flag.",
  "title": "Pipeline",
  "updatedAt": "2026-05-13T19:14:54.389Z"
}