Meaning
Defining and managing CI/CD pipelines as code (e.g., YAML DSL) rather than via manual UI configuration.
Primary Function
Define, version, and manage CI/CD pipelines through code.
Communicative Purpose
To describe the practice of treating pipeline definitions as version-controlled code.
Pattern
Define pipeline in YAML → commit to version control → CI system triggers builds
Função primária
Define, version, and manage CI/CD pipelines through code.
Propósito comunicativo
To describe the practice of treating pipeline definitions as version-controlled code.
Situações de gatilho
When setting up CI/CD pipelines, needing version control, reproducibility, and collaboration.
Contextos
DevOps, CI/CD pipelines, infrastructure as code, software delivery pipelines.
Padrão
Define pipeline in YAML → commit to version control → CI system triggers builds
Colocados típicos
- Jenkinsfile
- .gitlab-ci.yml
- Azure Pipelines YAML
- CircleCI config
Substituições comuns
- pipeline definition
- pipeline definition as code
Erros comuns
Hardcoding secrets in pipeline files, treating pipeline as immutable after deployment
Similar / contraste
pipeline via UI, manual pipeline configuration
Interferências
Coming from Jenkins scripted pipelines (Groovy): you may write imperative script blocks, but declarative YAML pipelines require a declarative structure and avoid embedded scripts.
Família do chunk
- infrastructure as code
- configuration as code
- policy as code
Nuance
Emphasizes version control, reproducibility, and collaboration.
Efeito pragmático
Encourages treating pipeline definitions as first‑class code artifacts.
Dica de memória
Think of 'pipeline as code' like 'infrastructure as code' but for CI/CD.
Nota
Avoid hard‑coding secrets in pipeline files; use the CI system's secret management features or external vaults.
Upgrade path
pipeline as code → GitOps / progressive delivery
Log in to save chunks.