Download to read offline
Uploaded byAgileSparks
Augury's Journey Towards CD by Assaf Mizrachi
Augury is moving towards continuous delivery (CD) of software by implementing several phases. Phase 1 involves building quality into the development process by having developers own quality assurance rather than having a separate QA team. Phase 2 breaks features into smaller, independently deployable units that can be deployed to production by developers to get faster feedback. This moves development closer to production and allows monitoring code behavior in production. It also separates deployment from releases using feature flags. These changes have resulted in developers feeling more impactful and skilled as the company has moved to continuous delivery.
More Related Content
Similar to Augury's Journey Towards CD by Assaf Mizrachi
Augury's Journey Towards CD by Assaf Mizrachi
- 1. Augury Journey TowardsCD AgileSparks May 2019
- 2. Augury Confidential COLLECT Smart sensorsmonitor your machines 24/7 ANALYZE Algorithms predict malfunctions and provide alerts VISUALIZE Full visibility of machine health across your facilityPREDICT MACHINE FAILURES
- 3.
- 4.
- 5.
- 6.
- 7.
- 8. SunSun Squad B Sun Squad CSquadA Squad D Wed Wed Wed Squad A Squad B Squad D Unite QA Effort Manual Regression Manual Regression Release Trains
- 9. Release Version XXX ReleaseVersion XXX + 1
- 10. Ice Cream ConeAnti-Pattern
- 11.
- 12. Local Env Squad Env CI Staging 1 2 3 4 5 6 Production ReleaseProcess Development Process
- 13. Quality Deployment Design Too Many HandoffsDuring Development
- 14. Augury Confidential Developer InThe Center
- 15. What to build?? How to build?? Isit working?? Is it deployed yet?? How is it in production?
- 16. Take active partin shaping impactful product Design & Write clean, simple and testable code. Own code quality Deliver to Production Monitor and track deliverables behaviour and usage
- 17. Developer Growth == Shorter HighQuality Delivery Cycles
- 18. Fast and SafeDevelopment. Developer Growth. Data Driven. Fast Feedback Loop In Every Step.
- 19. Augury Confidential Phase 1- Built-In Quality Development Release
- 20. Developers Own Quality. QA= Quality Assistance != Quality Assurance
- 21.
- 22. Code Reviews AsPart of CI
- 24. Augury Confidential Phase 2- Break It, Ship It Break It Ship It Closer to Production
- 25. Break It downinto smaller pieces In order to eliminate release idea, reduce delivery risk and achieve a faster feedback loop, we should breakdown feature into small decoupled, testable and shippable units. Once a unit is implemented and tested it should be deploy to production by the developer. Each delivered unit can have immediate or “eventual” impact
- 26. Closer to production Oncethe developer ships code frequently into production, monitoring code’s behaviour in production becomes a habit which is streamlined into the development life-cycle. Receiving fast feedback from the production environment is extremely powerful practice. Closer to Production
- 27. Separate deployment fromrelease By using tools such as feature flags we can avoid code aggregation in branches which is bad practice. The ability to integrate our code into production with limited activation is powerful tool and enabler for actual testing in production.
- 28.
- 31.
- 32. ● Developers cando QA to their own code. ● Sharing half-baked things is not easy for most of developers ● Wonderful things happens when developers are minutes from production ● Developers feels more impactful and skilled since we moved to CD
- 33.
- 34.
- 35.