Fear, Uncertainty, and Continuous Deployment

It's "easy" to apply CD to greenfield services, but that's not terribly helpful to all of the existing code out there. This talk includes examples and techniques for introducing CD tooling to engineers, verifying behavior of automation concurrently to existing processes, and keeping stakeholders calm and business needs met throughout the drive to faster delivery and value.

Transcript

1. Eric Sigler, Head of DevOps, PagerDuty @esigler Fear, Uncertainty, and Continuous Deployment
3. @esigler
4. @esigler
5. @esigler
6. @esigler Reduce code inventory
7. @esigler https://puppet.com/resources/white-paper/2016-state-of-devops-report
8. @esigler
9. @esigler You don't need 100% test coverage
10. @esigler
11. @esigler Keep your deployment instrumentation simple
12. @esigler Declare a Continuous
 Deployment holiday
13. @esigler “Ignore the engineer
 behind the curtain”
14. @esigler
15. @esigler
16. @esigler
17. @esigler Don’t need 100% test coverage Keep rollout simple to start Practice before writing tools Exercise coordination Be fair in workload
18. @esigler Thanks!
19. @esigler Resources • https://www.flickr.com/photos/codepo8/6697021447 • https://www.flickr.com/photos/thefangmonster/8432392004 • https://commons.wikimedia.org/wiki/File:X2_warehouse.jpg • https://commons.wikimedia.org/wiki/File:Continuous_Delivery_process_diagram.png • https://www.instagram.com/p/BKzK_37B_VC/ • http://www.resistors-and-diodes-and-picchips-oh-my.co.uk/wp-content/uploads/2011/05/ supercoder_2000_binary_keyboard.jpg • https://commons.wikimedia.org/wiki/File:Jazda_na_suwak_ulica_Starzy%C5%84skiego_wjazd_na_Most_Gda %C5%84ski_w_Warszawie.JPG • https://twitter.com/skylerfoxy/status/579039994184089600