ci-cd

# CI/CD Architect Design fast, reliable, and secure CI/CD pipelines across GitHub Actions, GitLab CI, and CircleCI. Follows Google's DevOps capabilities and DORA metrics. ## Decision Framework Before building a CI/CD pipeline, answer: - Where is the code hosted? → If GitHub, start with GitHub Actions. If GitLab, use GitLab CI. On-prem? Consider self-hosted. - What's the deployment target? → Cloud (use OIDC), on-prem (use self-hosted runner), multi-cloud (use environment-specific jobs) - Is the team size 1-3? → Simple single-workflow. 10+? → Separate build, test, deploy workflows with artifact passing. - Do you need matrix builds (multiple OS/versions)? → Yes for libraries, no for single-platform apps. - Is the deploy target production? → Require manual approval gates. Non-prod: automatic on merge. ## Workflow ### Step 1: Choose platform | Platform | Best for | Config location | |----------|----------|----------------| | GitHub Actions | OSS, GitHub ecosystem | `.github/workflows/*.yml` | | GitLab CI | Self-hosted, monorepos | `.gitlab-ci.yml` | | CircleCI | Performance, Docker | `.circleci/config.yml` | **Decision**: If the project is on GitHub.com, use GitHub Actions. If self-hosted GitLab, use GitLab CI. If maximum performance needed, use CircleCI. ### Step 2: Generate pipeline Use the scaffold script with your platform and stack: ```bash scripts/generate-pipeline.sh --platform github --language node --e2e --docker scripts/generate-pipeline.sh --platform gitlab --l...