Driving Continuous Delivery: Trunk-Based Deployment Strategies with PipeCD in Large Scale
summary
Case study of ABEMA uses PipeCD to implement trunk-based deployment plus progressive delivery across Kubernetes (EKS) and serverless (Lambda). Artifacts are built on PR merge, PipeCD’s event-watch updates manifests and triggers either pipeline sync canary pipelines or quick sync, with metric-driven automated deployment analysis that rolls back on anomalies. The platform manages ~130 microservices and cuts conflicts and release latency, achieving about 22 releases per day in production.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:48Productivity and reliability in CD
- 3:40Trunk-based deployment
- 5:52P CD for multi-platform
- 7:17Trunk-based with P CD
- 11:35P CD sync strategies
- 13:28Automated rollback in production
- 14:35Dev and Prod simultaneous deploy
- 15:37Results and future expansion
related talks
28mMinimum Viable Continuous Delivery
32mEvent-based Continuous Delivery: The End of the Monolithic Pipeline
34mBeyond Continuous Delivery
05mDelivery-Transformation DevOps-Pipeline
01h 01mA team's transition to Continuous Delivery
05mProject Lightning Talk: GitOps Without Boundaries: Deploy to Infrastructur...
30mModern Continuous Delivery
09mTrunk-Based Continuous Deployment in a Bank
