Reusable CI/CD Workflows
Reusable GitHub Actions pipelines with SonarQube quality gates, Trivy scanning, and zero-downtime deployment controls.
- GitHub Actions
- SonarQube
- Trivy
Overview
TODO: 2-4 paragraphs on why reusable workflows were needed (how many repos/teams, what was duplicated before) and what the library covers.
Architecture
TODO: describe the reusable workflow structure (composite actions vs. reusable workflows), the SonarQube quality gate step, the Trivy scanning stage, and how deployment controls enforce zero-downtime rollout.
Key decisions & tradeoffs
TODO: e.g. reusable workflows vs. a shared Action, how gate failures block merges, versioning/pinning strategy for consuming repos.
Results
TODO: quantify the outcome — pipeline setup time saved, number of repos adopted, defect/vulnerability catch rate, etc.