Continuous delivery intro by bob small
Download as PPTX, PDF2 likes506 views
This document discusses continuous delivery (CD) from a QA engineer's perspective. It introduces the concepts of continuous integration (CI) and CD, provides resources like a book and cartoons to further explain CD, and notes that CD can be implemented at varying levels of complexity. It also poses several questions to assess how close an organization is to achieving true CD, such as how frequently code is checked into trunk and whether tests are fully versioned along with code, configuration, environment and data.
Continuous delivery intro by bob small
- 1. Continuous Delivery A QA Engineers View
- 2. CI or CD • Martin Fowler Style - http://www.thoughtworks.com/continuous- delivery
- 3. CD or CD?
- 4. The Book
- 5. Cartoons explain a lot • http://continuousdelivery.com/
- 6. As complex as you want
- 7. Pop Quiz • How many THINK they are CI? • How many THINK they are CD? • How many THINK they are the other CD? • Are you Sprinting? • How many times per day do you check-in to Trunk? • Are your tests versioned, with the code, config, environment, and data?
- 8. The Gateways
- 10. Tools!
- 12. Mindset Change • Test cycles to a Subway train/Monitoring
- 13. Regression 24/7
- 14. Questions?
Editor's Notes
- #3: http://blog.assembla.com/AssemblaBlog/tabid/12618/bid/92411/Continuous-Delivery-vs-Continuous-Deployment-vs-Continuous-Integration-Wait-huh.aspx Continuous Integration is the practice of merging development work with a Master/Trunk/Mainline branch constantly so that you can test changes, and test that changes work with other changes. Continuous Delivery is the continual delivery of code to an environment once the developer feels the code is ready to ship.
- #4: Continuous Delivery is the continual delivery of code to an environment once the developer feels the code is ready to ship. Continuous Deployment is the deployment or release of code to Production as soon as it is ready.
- #5: https://www.youtube.com/watch?v=ZLBhVEo1OG4
- #6: Continuousdelivery.com
- #8: CI = continuously integrate changes into environments (code, build, test) CD = continuously deploy changes into environments (code, build, test, release) CD&D = continuously deployment to production (code, build, test, release, in production)
- #9: Where are your test being automated? Are you running automated tests hands free or hands on? Why?
- #15: What about Data overload? What about tests that need maintenance? What about notifications?