Your SlideShare is downloading. ×
0
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Continuous deployment
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Continuous deployment

6,563

Published on

A 20 minute talk I gave as part of the "Code as Craft: Moving Fast at Scale" Etsy micro-conference

A 20 minute talk I gave as part of the "Code as Craft: Moving Fast at Scale" Etsy micro-conference

Published in: Technology
0 Comments
13 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
6,563
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
96
Comments
0
Likes
13
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Continuous Deployment kellan@etsy.com, @kellan, VP of EngineeringThursday, March 17, 2011
  • 2. What? => Why? => How?Thursday, March 17, 2011
  • 3. What is it?Thursday, March 17, 2011
  • 4. Small, frequent changes. To production.Thursday, March 17, 2011
  • 5. Small Frequent Small, frequent changes. To production.Thursday, March 17, 2011
  • 6. A collection of techniques to avoid SUCKING.Thursday, March 17, 2011
  • 7. Why do we do it?Thursday, March 17, 2011
  • 8. Agility: Always Be ShippingThursday, March 17, 2011
  • 9. MTTD / MTTRThursday, March 17, 2011
  • 10. 4 change related “incidents” in 2010Thursday, March 17, 2011
  • 11. time to detect: <15 minutes time to resolve: ~216,000 minutes Deep Water HorizonThursday, March 17, 2011
  • 12. mean time to detect: < 5 minutes mean time to resolve: MMTR: 4.5 minutes MTTD: <5 minutes 4.5 minutesThursday, March 17, 2011
  • 13. Encourages ExperimentationThursday, March 17, 2011
  • 14. 1%Thursday, March 17, 2011
  • 15. Optimize for Developer HappinessThursday, March 17, 2011
  • 16. DevOpsThursday, March 17, 2011
  • 17. Scales Trust and RiskThursday, March 17, 2011
  • 18. How do we do it?Thursday, March 17, 2011
  • 19. Work in trunk, branch in code.Thursday, March 17, 2011
  • 20. “All existing revision control systems were built by people who build installed software” - Paul Hammond, Always Ship Trunk, Velocity 2010Thursday, March 17, 2011
  • 21. if ($cfg[‘awesome_new_search’]) { # new hotness $rsp = do_solr(); } else { config flags # boring old stuff $rsp = do_grep(); }Thursday, March 17, 2011
  • 22. one install, multiple versions.Thursday, March 17, 2011
  • 23. Keep it simple.Thursday, March 17, 2011
  • 24. One button deployThursday, March 17, 2011
  • 25. Operability ReviewThursday, March 17, 2011
  • 26. CommunicationThursday, March 17, 2011
  • 27. Graph Everything!Thursday, March 17, 2011
  • 28. FAQ: Schemas? Testing and continuous integration? QA?Thursday, March 17, 2011
  • 29. /trunk/, config flags, 1B deploy, what could go wrong?, IRC, graphsThursday, March 17, 2011

×