Continuous Deployment Workflows

on YouTube ↗46m

" summary

Argues that shipping dozens of tiny releases per day is practical by removing release branches and deploy on merge so every merged branch automatically goes to prod, backed by an automated CD pipeline, fast reversible deploys, and comprehensive tests (unit, E2E, visual with Percy, Lighthouse performance checks). Recommends small task branches that merge within 2–3 days, feature flags, and per-branch preview environments using containerized forks of production data (Netlify and DB fork services cited) to get fast user feedback and lower deployment risk.

AI-written summary · about

" chapters (10)

1. 0:00Introduction and welcome
2. 1:47Classic deployment workflow explained
3. 4:15Problems with classic workflow
4. 10:43What is continuous deployment
5. 14:19Splitting work into small steps
6. 20:14Requirements for continuous deployment
7. 24:22Automated testing in CD
8. 35:00Adopting continuous deployment
9. 40:38Benefits and closing remarks
10. 41:40Q&A session

" related talks

• 44mI Deploy On FridaysMichiel Rook · Dutch PHP Conference 2017
• 40mContinuous Delivery Anti-PatternsJeff Morgan · Agile Testing Days 2016
• 36mContinuous Deployment with RailsSebastian von Conrad · RubyConf AU 2014
• 51mBetter software, faster: principles of Continuous Delivery and DevOpsBert Jan Schrijver · Devoxx Belgium 2019
• 31mFireside Chat: Continuous DeploymentValentina Servile · XConf Europe 2024
• 47mContinuous Delivery WarstoriesAllan Ebdrup · GOTO Copenhagen 2015
• 24mContinuous Deployment at ScalePremshree Pillai · PHPConf.Asia 2016
• 01h 01mI deploy on Fridays (and maybe you should too)Michiel Rook · DevOps Conference 2018