CI/CD (Continuous Integration / Continuous Deployment)
CI/CD is a method to frequently deliver apps to customers by introducing automation into the stages of app development.
Components: 1. Source Control (Git). 2. Build Server (CI). 3. Artifact Registry (Docker Hub, Artifactory). 4. Deployment Orchestrator (Kubernetes, AWS). Stages: Commit -> Build -> Test -> Stage -> Production. Concepts: Triggers, Runners, Secrets, Parallelism.
graph LR
Center["CI/CD (Continuous Integration / Continuous Deployment)"]:::main
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧒 Explain Like I'm 5
Imagine a factory that makes cars. If the workers had to stop every time they fixed a small bolt to manually inspect the whole car, it would take forever. CI/CD is like an automated assembly line with sensors at every step. If a bolt is loose, the sensors instantly sound an alarm (CI). If everything is perfect, the car is automatically driven out of the factory and delivered to the customer (CD), without any extra paperwork.
🤓 Expert Deep Dive
A robust CI/CD pipeline is built on 'Pipeline as Code' (YAML/Groovy). Jenkins, GitLab CI, and GitHub Actions allow developers to define build stages (Lint, Unit Test, Integration Test, Build Artifact, Security Scan, Deploy). Key metrics include 'Lead Time for Changes' and 'Change Failure Rate'. Sophisticated CD setups use 'Canary Deployments', where new code is initially served to only 1% of users, or 'Blue-Green Deployments', which switch traffic between two identical environments. To ensure security, 'DevSecOps' practices integrate secret management (Vault) and static/dynamic analysis (SAST/DAST) directly into the automation flow.