Continuous Delivery at 7digital

TDD Cycle Continuous Delivery at 7digital An experience report Chris O'Dell @ChrisAnnODell How long would it take your organization to deploy a change that involved just one single line of code? Do you do this in a repeatable, reliable manner? Question? Half a day. Small changes reduce risk Remove fear of change Move faster Fast feedback Why bother? Manually updated shared libraries Lots of legacy code Shared testing resources e.g. Databases. More time fixing bugs than adding features Everything broken Where we came from A Day in the Life of a Change... No Feature Branches All builds must be green No releases after 4pm No releases on a Friday Rules! Where we are now Automated updating of shared libraries Shared build and deployment scripts Scripted Database Creation (DBMigraine) One-Button deployments Walking Skeletons for all new projects Any questions? Half a day. Where we're going Reduce number of legacy shared libraries SOA architecture of focused APIs Clean-up & test shared scripts Automate creation of servers Increase Live monitoring @ChrisAnnODell Deployment Pipeline Automation Reliable & repeatable Low cycle time Reduces inventory & obsolescence What is it? Architectural shift to SOA Slow process Got far worse before it got better Perseverance Making the change End-to-end tests Acceptance Tests Unit Tests Unit Tests Acceptance Tests End-to-end tests Not there, yet Automated shared libraries hides real problem Shared scripts untested & bloated Last few pieces of monolithic API Development Source Control Build & Unit Test Acceptance Tests QA Deploy! Build & Unit Tests Acceptance Tests Change how we work Smaller, focused teams Reduced size of work items Introduced Kanban Focused on Technical debt Go slower to move faster