Continuous delivery made possible
- 1. Continuous Delivery made possible Domenico Musto @mimmozzo domenico.musto@gmail.com
- 2. What do I do ? .NET C# Team leading Web REST Ruby Automation Testing Agile
- 3. What is continuous delivery ?
- 5. Continuous integration Continuous deployment
- 6. Continuous integration Continuous deployment Continuous delivery
- 7. Continuous integration The process of frequently integrating the code you are working on with everybody else’s code
- 8. Continuous deployment automatically deploy on an integration test environment the "integrated code" have a reasonable automated way of deploy software to a production environment
- 9. Continuous delivery The ability to easily and quickly ship new value/features to customers at any point in time
- 10. Easily and quickly - Being able to deploy in less than 5 minutes (automated)
- 11. Easily and quickly - Being able to deploy in less than 5 minutes (automated) - Being confident that the software you are deploying has passed a well defined test suite
- 12. Easily and quickly - Being able to deploy in less than 5 minutes (automated) - Being confident that the software you are deploying has passed a well defined test suite - Being able to immediately collect info about the new version of the software
- 13. Easily and quickly - Being able to deploy in less than 5 minutes (automated) - Being confident that the software you are deploying has passed a well defined test suite - Being able to immediately collect info about the new version of the software - Being able to quickly rollback to the previous version in a matter of minutes in an automated way
- 14. continuous integration and continuous deployment enable continuous delivery
- 15. Why do I care about all this ?
- 16. 50%
- 17. It’s about build the right thing
- 18. 35%
- 19. Reduce costs and risk by delivering small incremental changes
- 21. Motivation
- 22. How do I get there ?
- 23. How do I get there ? - CD is not for every single business
- 24. How do I get there ? - CD is not for every single business - It’s a cultural change
- 25. How do I get there ? - CD is not for every single business - It’s a cultural change - It takes time, and it will hurt you
- 26. How do I really get there ? - Split up the monolith
- 27. How do I really get there ? - Split up the monolith - Enable continuous integration
- 28. How do I really get there ? - Split up the monolith - Enable continuous integration - Enable continuous deployment
- 30. Feature branching vs branching by abstraction
- 31. by Martin Fowler
- 32. by Martin Fowler
- 33. by Martin Fowler
- 34. by Martin Fowler
- 35. by Martin Fowler
- 38. DEVELOPER RUN TESTS LOCALLY COMMIT UNIT TESTS BUILD CI TOOL PACKAGE
- 41. Packaging
- 42. Automatic installation and configuration
- 43. Database
- 44. Blue Green
- 46. Decouple release from deployment
- 47. Deploy pipeline
- 49. Tools - TeamCity - Artifactory - Chef - Vagrant - Go
- 50. DEVELOPER RUN TESTS LOCALLY PACKAGE TEST CHEF VAGRANT COMMIT
- 51. TEAMCITY PACKAGE GO DEPLOY INTEGRATION TEST INTEGTATION DEPLOY STAGE TEST STAGE DEPLOY PRODUCTION TEST PRODUCTION
- 52. Let's wrap it up - Continuous integration (step by step) - No feature branching - Packaging - Integration pipeline - Continuous deployment (step by step) - Self installable components - Deploy pipeline - Provisioning
- 53. Thanks
Editor's Notes
- #2: 1
- #3: 2
- #4: 3
- #5: 4
- #6: 5
- #7: 6
- #8: 7
- #9: 8
- #10: 9
- #11: 10
- #12: 11
- #13: 12
- #14: 13
- #15: 14
- #16: 15
- #17: 16
- #18: 17
- #19: 18
- #20: 19
- #21: 20
- #22: 21
- #23: 22
- #24: 23
- #25: 24
- #26: 25
- #27: 26
- #28: 27
- #29: 28
- #30: 29
- #31: 30
- #32: 31
- #33: 32
- #34: 33
- #35: 34
- #36: 35
- #37: 36
- #38: 37
- #39: 38
- #40: 39
- #41: 40
- #42: 41
- #43: 42
- #44: 43
- #45: 44
- #46: 45
- #47: 46
- #48: 47
- #49: 48
- #50: 49
- #51: 50
- #52: 51
- #53: 52
- #54: 53