Successfully reported this slideshow.
Your SlideShare is downloading. ×

Continuous Deployment

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Upcoming SlideShare
Continuous Deployment
Continuous Deployment
Loading in …3
×

Check these out next

1 of 32 Ad

More Related Content

Slideshows for you (20)

Viewers also liked (20)

Advertisement

Similar to Continuous Deployment (20)

Advertisement

Recently uploaded (20)

Continuous Deployment

  1. 1. Continuous Deployment<br />(http://) Timothy Fitz (.com)<br />
  2. 2. Quick Survey<br />
  3. 3. Overview<br />Problems<br />Pillars<br />Practices<br />
  4. 4. Problems in Software Development<br />Regressions<br />Readiness<br />ODD<br />
  5. 5. Regressions<br />
  6. 6. Readiness<br />
  7. 7. Opinion Driven Development<br />
  8. 8. Ship more frequently<br />
  9. 9. Continuous Deployment<br />
  10. 10. Discontinuous Deployment<br />
  11. 11. Discontinuous Deployment<br />
  12. 12. Discontinuous Deployment<br />
  13. 13. The Wild West<br />
  14. 14.
  15. 15. +Automated Tests<br />
  16. 16. Automated Tests<br />Unit Tests<br />Integration Tests<br />Regression Tests<br />
  17. 17. Automated test runner<br />
  18. 18. Follow Every Test Failure<br />
  19. 19.
  20. 20. Slow query<br />
  21. 21. +Production Immune System<br />
  22. 22. Immunization<br />
  23. 23. Timebomb<br />
  24. 24. +Production Monitoring<br />
  25. 25. Business Regressions<br />
  26. 26. Continuous Deployment<br />
  27. 27. Practices<br />Code-specified Feature Rollout<br />Root cause every production failure<br />
  28. 28. Humans?<br />Business Facing<br />Support<br />Programming<br />Critique<br />Product<br />Technology Facing<br />-Poppendieck<br />
  29. 29. Rollout Process<br />
  30. 30. Regression in production?<br />Trace the path<br />Five whys<br />
  31. 31. How do you get there?<br />Know that it’s possible.<br />Start small, today.<br />Go for incremental benefit.<br />
  32. 32. Q&A <br />

Editor's Notes

  • Introduce self.Thank people.Did not invent CD, props to IMVUBottom line: I’m giving this talk because I want people to ship faster.
  • Show of handsHow many are agile?Who is using Continuous Integration?Everyone raise your hands. If you haven’t shipped in the last 2 years put your hands down.12 month. 6months. 2 months. 1 months. Make sure to, for the camera and the audience, say approximately what’s going on.3wk? 2wk? 1wk? Daily? More frequently?
  • Waste around bugs, both those you forgot to fix and those you fixed that didn’t matter.
  • “Non-functional requirements”Transition: ODD
  • HiPPoSide note: stock photo not ironic msftTransition: So what’s the answer?
  • Give definition of CD.It’s about information.Transition: CD is a highway at it’s best, 75mph, no stopping.
  • Continuous Integration is a prerequisite
  • Fundamentally what is CD? Ship live as fast as possible.
  • Defeated by the typo/off-by-one error
  • Code, Class, Specific CauseForces great test coverageTransition: Now you have to listen to your system
  • Can’t afford to roll through red lights.Sounds like more work and initially it isPays ofTransition: permission to rock
  • Measure everything importantMeasure hostsMeasure business metricsDark launchFree to make mistakesSafety netBe more aggressiveWrench: Schemas? Schema-less, RethnkDB, key-value on top of MySQL (Friendfeed)
  • How bug free should the product be?
  • Transition: The most common question I get: is there no QA staff anymore?
  • Interest in Selenium lessons learned talk

×