CI and CD as a Service: A multi-vendor driven system
summary
A blueprint for a CI/CD-as-a-service that stitches multiple vendor deliveries into a single release pipeline, preserving vendor autonomy while removing manual pulls and version drift. Repositories hold manifests and content, the central system performs auto-pull manifests, runs image code manifest scans and peer reviews, promotes artifacts through v1 alpha→beta→GA tags, and supports canary deployments, RBAC and network policies on Kubernetes. Two implementations use vendor-built pipelines: one with Spinnaker + Argo CD + Airship, the other with a self-contained deploy artifact plus Airship; this is a design proposal rather than production metrics.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:51Agenda
- 2:12Need for CI/CD as a Service
- 4:36Typical Requirements
- 7:13Vendor CI & Onboarding (1/2)
- 11:35SW Test, QA and Progression
- 13:41Deployment in Production
- 15:32Implementation Approaches (1/2)
- 19:11Conclusion
related talks
23mCI/CD: Conscious Uncoupling
22mCI/CD is now AI/CD
40mMicroservice Continuous Delivery
08mCI/CD Is Now AI/CD
57mPipelines: Everything Everywhere All At Once
32mWest Side CD: The Deployment Ballet Goes On
30mModern Continuous Delivery
17mDriving Continuous Delivery: Trunk-Based Deployment Strategies with PipeCD in Large Scale