Continuously delivering software to big brands
summary
Codeweavers runs a CI/CD pipeline built on .NET, ASP.NET MVC/Web API, SQL Server/Cassandra/Postgres, Angular and Visual Studio, with Subversion over Git and a forked CruiseControl.NET driving per-app 4 minute builds. Commits trigger unit/Selenium/SpecFlow tests, demo deploys and an automated rolling live deploy; Selenium runs against a mocked service cache to reduce flakiness. Average commit-to-live is about 7.5 hours (urgent fixes in ~15 minutes), with teams blocked from committing when the build is red.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:45Three step plan
- 1:14Pauls background
- 2:57Delivering software
- 4:10Big brands
- 8:04Lower cycle time
- 9:27Tools
- 11:28Continuous Integration
- 16:56Committing
- 19:35CI
- 24:44Deployment
- 29:54How does it work
- 36:34Cycle time
- 41:07Risky
- 41:37Clients benefits
related talks
49mContinuous Delivery for Legacy Code
47mContinuous Delivery Warstories
01h 01mA team's transition to Continuous Delivery
51mBetter software, faster: principles of Continuous Delivery and DevOps
48mContinuous Delivery: Tales from Windowsland
46mThe Software Factory
25mProgramming to the extreme
49mContinuous Delivery for Legacy Code