A Teams Transition to Continuous Delivery
- 1. Transition to Continuous Delivery Ashley Noble @anobleperson #ndcsydney
- 2. “Continuous Delivery is the ability to get changes… into production, or into the hands of users, safely and quickly in a sustainable way” Jez Humble
- 3. https://upload.wikimedia.org/wikipedia/commons/3/3b/Internet_et_ses_applications.png
- 4. Two years ago… 6 developers 1 Large solution Semi Automated build 100s of AUTs Manual deployment Bi-weekly deploys Hours to deploy Multiple wikis, 10s of steps Days to test and validate
- 5. + +
- 7. The present… 15 developers Multiple Solutions Totally automated build 1000s of AUTs Fully automated deployment 22 deployments a day 3 to production a day 100s of Acceptance Tests
- 10. Reduce work in progress Smaller work packets Delivering value earlier Automation of all things
- 11. Continuous Integration Automated Acceptance Tests Deployment Pipeline
- 12. Continuous Integration Find and fix errors quickly Reduce integration pain Find integration issues early Every process is leaner Integrate code to a shared repository regularly, usually daily or more frequently
- 14. After – Continuous Integration (ish)
- 15. “you can't effectively address cultural problems with process, just as you can't effectively address process problems with culture” Kent Beck
- 18. Build and Package Versioning GitVersion to the rescue!
- 24. Transient Failures in AATs
- 25. QA Team?
- 26. Continuous Delivery or Continuous Deployment?
- 30. Feature toggling
- 32. 31 GIT & Review Application
- 33. Metrics and Dashboarding More Instrumentation Predictive Log Analytics Improving existing processes
- 34. Building a CICD pipeline was a journey Made incremental steps towards the destination
- 35. Thanks!