Continuous Deployment

Transcript

1. Continuous Deployment
2. Matt White @whitethunder922 github.com/whitethunder
3. What is meant by “Continuous Deployment?”
4. From Timothy Fitz: •Continuously integrate (commit early and often) •On commit automatically run all tests •If the tests pass deploy to the cluster •If the deploy succeeds, repeat
5. How often do you deploy?
6. Our Journey to Continuous Deployment
7. Things We Needed • Simplified Release Process • Thorough Testing • Continuous Integration • Monitoring All things we should have anyway
8. Simplified Release Process
9. Make Releases Less Like This
12. Thorough Testing • Not necessarily 100% test coverage • Tests that do what your users do
13. Fast and Efficient Tests • Profiling • Don't disguise integration tests as unit tests (isolate) • Avoid test duplication • Create fewer objects • Load dependencies as needed • Don't test/use Rails
14. Continuous Integration
15. CI Should Be Fast Previous CI Server: • Quad-Core AMD Opteron(tm) Processor • 16GiB RAM • Rackspace Cloud instance • 30 minutes to run tests Current CI Server: • 16 Core Intel(R) Xeon(R) CPU 2.40GHz • 32GiB RAM • SSD • 7 minutes to run tests
16. Make Use of Multiple CPU Cores
17. parallel_tests
18. hydra
19. Monitoring • A user should not be the first one to notify you that something broke • Something automatic should freak out when stuff breaks
21. New Relic
22. New Relic
23. Excuses • More releases would be more pain • Our tests are insufficient • Our users/stakeholders won't be cool with it
24. rollout
25. Benefits • Waste is reduced • Fail fast • Encourages working in smaller increments
26. Result
27. MOAR PONIES!!!11! Who couldn't use moar ponies??!!?
28. Questions? Matt White @whitethunder922 github.com/whitethunder