Continuous Delivery and DevOps and Robots; Oh my!
summary
Domain migrates 100+ .NET apps to a microservice platform with infrastructure-as-code so teams push code and AWS CloudFormation plus PowerShell DSC boots clusters automatically. CI/CD uses TeamCity/Bamboo → TeamCity, Octopus Deploy for multi-tenant hot‑swap releases, NuGet packaging, feature toggles, Pingdom/New Relic monitoring and Slack/opsgenie alerts. A sample app drops from half‑day deploys to 46 seconds; the fleet averages ~64 deployments/week with a record of 150 deployments in one week. Robot Army is self‑provisioning, tested with Pester and cost‑optimized.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:52Domain group
- 7:20Cultural Challenges
- 9:03WHATS DEVOPS
- 9:37Lean Six Sigma: 8 Wastes
- 10:53Three Generations of Applied Laziness
- 12:03Continuous Delivery Pipeline
- 12:53Octopus Deploy vs. Build Servers
- 15:05Infrastructure Toolchain
- 16:02Cultural Changes
- 18:22Three Steps to High Velocity
- 27:13Build Toolchain
- 31:49Deployment Flow
- 33:06Standard Windows Cluster
- 35:16Introducing the Robot Army!
- 36:09Cluster Provisioning
- 36:53Monitoring
- 38:41Project Sauron
- 41:35New Branching Strategy
- 42:33Octopus Lifecycle Policies
- 43:20Cluster Definition
- 44:10Example Robot Platoon Declaration
- 46:03High Availability Octopus Cluster
- 49:50Cost Saving Strategies
- 55:22The Domain Train
- 56:22Dance 2 Deploy
related talks
30mBringing DevOps Success to Every App, Tool & Role in Your Org
47mArchitecting for DevOps and Continuous Delivery
01h 31mAccelerate Business Delivery With AI and DevOps
01h 01mA team's transition to Continuous Delivery
49mThe road to continuous deployment: a case study
48mContinuous Delivery: Tales from Windowsland
51mGet up to speed with DevOps using modern development practices
01h 03mContinuous Delivery in Azure