🎁 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

Nginx
A high-performance web server and reverse proxy known for its stability, low resource usage, and ability to handle many concurrent connections.
Blue-Green Deployment
A deployment strategy using two identical environments where traffic is switched from the old version to the new one instantly.
Canary Deployment
A deployment strategy that gradually rolls out changes to a small subset of users before deploying to the entire infrastructure.
Istio
An open-source service mesh that provides traffic management, security, and observability for microservices on Kubernetes.
Environment Variable
A dynamic value stored outside the application code that configures behavior without hardcoding sensitive or environment-specific data.
Infrastructure as Code (IaC)
The practice of managing infrastructure through machine-readable configuration files rather than manual processes.
 View All DevOps Terms →