Continuous Integration & Delivery

Talk given at Tech Nottingham 2014-11 and DotNetSheff 2015-06.

Transcript

1. Continuous Delivery as a Service (and Continuous Integration)
2. Hi!
4. Topics Continuous Integration What? Why? How? Continuous Delivery
5. Continuous Integration What is it?
6. Continuous Integration The practice of integrating code into a shared repository several times a day
7. Continuous Integration Why do it?
8. CI: Why? Reduces long and complex merges, also known as “integration Hell”
9. CI: Why? Increases visibility
10. CI: Why? Catch issues early
11. CI: Why? Spend more time adding features and less time fixing bugs
12. CI: Why? Reduce time waiting for feedback
13. CI: Why? Increase overall confidence
14. CI: Why? Summary Reduce long & complex integrations Increase visibility Catch issues early Spend more time adding features, less bug fixing Reduce time waiting for feedback Increase confidence
15. Continuous Integration How is it done?
16. CI: How? Merge Build Test
17. CI: How? Merge Integrate several times a day
18. CI: How? Merge Build Test
19. CI: How? Build Automate the build process
20. CI: How? Build Build every commit on an integration machine
21. CI: How? Build Build quickly
22. xkcd.com/303
23. CI: How? Build Make the build status visible to everybody
25. CI: How? Merge Build Test
26. CI: How? Test “With testing, I know straight away when I added a bug. That lets me fix the bug immediately, before it can crawl off and hide.” - Martin Fowler
27. CI: How? Test Automate tests
28. CI: How? Test “...maintaining good regression tests is the key to refactoring with confidence.” - Andrew Hunt
29. CI: How? Test Test on a like-live environment
30. CI: How? Test Make the test status and results visible to everybody
31. CI: How? Test Archive build artefacts and test results in a shared space
32. CI: How? Test User acceptance test (UAT) and capacity test last
33. CI: How? Merge, Build, Test Be responsible
34. CI: How? Be Responsible Merge frequently
35. CI: How? Be Responsible Don’t commit a broken build
36. CI: How? Be Responsible Don’t commit failing tests
37. CI: How? Be Responsible Don’t “push and run”
38. CI: How? Summary Merge Merge several times a day Build Automate builds Build every commit on an integration machine Build quickly Keep builds status visible
39. CI: How? Summary Test Automate tests Test on a like-live environment Keep test results visible Archive build artefacts and test results Perform expensive tests last
40. CI: How? Summary Be Responsible Merge frequently Don’t commit a broken build Don’t commit broken tests Don’t “push and run”
41. Continuous Delivery What is it?
42. The practice of deploying all releasable code all the time Continuous Delivery
43. Initiate a deploy at the push of a button Continuous Delivery
44. Continuous Delivery How do you do it?
45. Use a build server CD: How? Build Servers
46. Use a build service CD: How? Build Servers
47. All together Continuous Integration Merge frequently, Automate builds, Automate tests Be responsible, don’t break the build Continuous Delivery Aim to deploy every commit (continuous deployment) Keep deployments trivial and low risk
48. Thanks! Questions? (and it’s time to get your laptop out)
49. Further Reading The Book: Continuous Delivery, J. Humble & D. Farley Thoughtworks, Continuous Integration & Delivery thoughtworks.com/continuous-integration thoughtworks.com/continuous-delivery MartinFowler.com martinfowler.com/tags/continuous%20integration.html