Continuous Delivery Transformation: The New Way of Working
summary
AdvancedMD integrates CloudBees Flow as a central orchestrator to turn a chaotic mix of PowerShell, Python, Chef, Ansible, Terraform and Artifactory into repeatable releases; a microservice template plus a self-service catalog spins up dev/test/stage/prod servers and enforces code-reviewed deployment scripts. The org scales from ~2 products to 20–25 products, implements Flow on AWS, sees measurable value in about 4–6 weeks of run time, but admits database CI/CD across petabyte datasets remains unresolved.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 2:02Our Journey
- 2:39Single Server Configuration
- 3:39Multiple Server Configuration
- 5:23Flow DevOps
- 7:18Life before Flow
- 8:12Walls of Confusion
- 8:36Multiple Teams
- 8:59Multiple toolsets
- 9:44The Late Late Show
- 10:21Challenges
- 13:43Collaboration
- 14:53Team Structure
- 15:50Do Not Change the Culture
- 18:52A Perfect World
- 21:25Introducing Flow
- 24:34Flows Differentiation
- 29:19DevOps Insight
- 33:16Conclusion
- 34:00QA
related talks
01h 01mA team's transition to Continuous Delivery
42mAutomation, Innovation and Continuous Delivery
24mWhy, What, and How of Continuous Delivery
01h 03mYet Another Continuous Delivery Talk
30mDevOps and Agility Immersed in the Production Factory
05mDelivery-Transformation DevOps-Pipeline
28mScale Your DevOps Initiative Beyond Its Awkward Teenage Years
49mIncubating Continuous Delivery