CI/CD: Conscious Uncoupling
summary
Splitting CI and CD into separate pipelines removes a single point of failure and lets CD start from the failure point without re-running unit tests and builds; CI handles pull-request triggered unit tests, code-quality scans, artifact/container builds and vulnerability scans, while CD watches tagged artifacts, runs templated deployments, automated smoke/functional tests, approval gates, rollbacks and APM-integrated performance verification. The setup also enforces segregated secrets and audit logs, produces deployment-time metrics per microservice, and reduces infra overhead by sharing runways.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:19Who am I
- 1:29CICD Definition
- 2:14CICD Pipelines
- 2:54Conscious Uncoupling
- 3:56Pipelines
- 4:45Process
- 7:23CD
- 16:35Improvements
- 21:35Conclusion
related talks
22mCI/CD is now AI/CD
42mCI/CD, is the Divorce Inevitable?
24mCI/CD Best Practices to Deliver Software Faster
22mCI and CD as a Service: A multi-vendor driven system
22mA Crawl, Walk, Run Story of CI/CD
48mCI/CD Security
32mPractical Tips & Tricks for CI/CD Success
38mCI is Essential but not Sufficient for an Effective Application Delivery Workflow