1 / 15

Continuous Delivery good & bad 4/20/2012

Continuous Delivery good & bad 4/20/2012. Kathleen Barrera CS577b Spring 2012. Overview. What is Continuous Delivery Scenario Definition How to do it well Where it can fail Conclusion Q&A. Imagine … . You are the project manager for the Virgin America booking system

ami
Download Presentation

Continuous Delivery good & bad 4/20/2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Continuous Deliverygood & bad4/20/2012 Kathleen Barrera CS577b Spring 2012

  2. Overview • What is Continuous Delivery • Scenario • Definition • How to do it well • Where it can fail • Conclusion • Q&A

  3. Imagine … • You are the project manager for the Virgin America booking system • Critical bug on phone app is incorrectly charging flights as $1000 instead of $100!!! • New feature that sends ticket coupons to anyone who tweets #virginamerica25coupon to compete with JetBlue

  4. But … • Your software release process is PAINFUL and SLOW • LOTS of integration bugs • Bugs in production cannot be reproduced in development

  5. Continuous Delivery • Software release needs to FAST and PAINLESS and.. RELIABLE

  6. Continuous Delivery “.. effective pattern for getting software [from] development to release” – 2010, Continuous Delivery, Farley & Humble

  7. Related Concepts • Continuous Integration • Test Driven Development • Test Automation • …

  8. How ? • Development • Continuous integration – integrate early and often • Keep builds fast • Build tests in

  9. How ? • Development • Version Control • Branch when necessary • Follow good configuration management practices • Manage Dependencies well (SOA, loosley coupled)

  10. How ? • Testing • Automated testing • Everyone owns the testing suite!

  11. How ? • Scripted build & deployment • Overnight builds • Push button deployment • Eliminate manualsteps

  12. But … • Instant deployment does not happen instantly • Need to refactor current deployment pipeline • May need to procure tools / hardware / training • ROI may be slow and gradual

  13. But … • Introduce more risk • Release too much instead of incrementally • Difficult to discover what broke what • Or … Users don’t want features!

  14. Conclusion • Continuous Delivery driven by BUSINESS • Goal/Question/Metric? • Continuous Delivery is owned by everyone on the team • Not one person’s job! • Continuous Delivery relies on collaboration at every stage and feedback and starts early in the development lifecycle

  15. Questions and Discussion

More Related