🎁 New User? Get 20% off your first purchase with code NEWUSER20 Register Now →
Menu

Categories

DevOps Beginner

What is Pipeline as Code?

Defining CI/CD pipeline configurations as version-controlled code files rather than through UI-based pipeline builders.

Pipeline as Code stores build, test, and deployment pipeline definitions in the same repository as application code. Examples include Jenkinsfile (Jenkins), .github/workflows/*.yml (GitHub Actions), .gitlab-ci.yml (GitLab), and azure-pipelines.yml (Azure DevOps). Benefits include version history of pipeline changes, code review for pipeline modifications, branch-specific pipeline variations, and reproducibility. Pipelines typically define stages (build, test, deploy), steps within stages, environment variables, triggers (push, PR, schedule), and conditions. Treating pipelines as code enables the same engineering practices (review, testing, rollback) applied to application development.

Related Terms

Canary Deployment
A deployment strategy that gradually rolls out changes to a small subset of users before deploying to the entire infrastructure.
Git
A distributed version control system that tracks changes in source code during software development.
GitOps
A practice where Git repositories serve as the single source of truth for both application code and infrastructure configuration.
Log Aggregation
The process of collecting, centralizing, and indexing log data from multiple sources for unified search and analysis.
Immutable Deployment
A deployment strategy where new versions replace existing instances entirely rather than updating them in place.
ArgoCD
A declarative GitOps continuous delivery tool for Kubernetes that automatically syncs cluster state with Git repositories.
 View All DevOps Terms →