Continuous Deployment @ Coolblue

Transcript

1. DEPLOYMENT. @ Coolblue.
2. PAUL. Technical Pathfinder
3. DEVELOPMENT
5. 30
 TEAMS
8. DEPLOYING SOFTWARE. Delivering packaged high quality software on servers.
9. • +/- 50 deploys per day on all platforms • Single button deployment • Developers do their own deployment FACTS AND FIGURES.
10. GATHER LEARNINGS FAST. By releasing often and quick.
11. LANGUAGE AGNOSTIC. Same principles apply.
12. DEVELOPING FEATURE 'X'. Smiling customers.
13. UNIT TESTS. All code is guilty, until proven otherwise.
14. CODING STANDARDS. Rules may apply.
15. More Octocats at https://octodex.github.com/
16. FORKS. Personal cutlery.
17. GITHUB FLOW. Fork & Pull model.
18. PULL REQUESTS. Share, review and discuss.
19. PULL REQUESTS. Small commits, small context.
20. TEAM CHECK. None of us is as smart as all of us.
21. QUALITY CONTROL. Check standards have been met.
22. BUILD SERVER. Construction completed.
23. TEAMCITY. Central point of inspection and deployment.
24. BUILD CHAINS. Sequence of build steps with specific purpose.
25. BUILD SCRIPTS. Describe automation workflow.
27. RECYCLE YOUR CONFIGURATIONS. Create a default for all projects and allow overrides.
28. BUILD CHAINS. Sequence of builds with specific purpose.
29. BUILD STEP 1. Continuous inspection.
30. • Automated tests • Unit testing • Functional testing • Static code analysers • Lint checkers • Code duplication checkers • Code sniffers • Code metrics QUALITY ASSURANCE.
31. BE LAZY; YOU DON’T HAVE TO DO IT YOURSELF Continuous inspection platform are becoming a service.
32. REPORTING ON EACH PULL REQUEST. Integrating all information available.
33. Examples: • Scrutinizer • SonarSource • Codacy CONTINUOUS INSPECTION PLATFORMS.
34. MERGE PULL REQUEST. Integrate into the main repository.
35. REMEMBER GITHUB FLOW. Merge it in the master branch of the original repo.
36. ACHIEVEMENT. Continuous integration.
37. BUILD STEP 2: PACKAGING. Not a box of chocolates..
38. • Close to the OS • RPMs distributed via own repository • Installed/Updated via OS package manager • Updates triggered via puppet run LINUX.
39. • Control over file permissions & rights • Clean uninstallation • Package managers are simple and well-known • Easily distributed • No added complexity of third-party tools RPMS ARE POWERFUL.
40. • Octopus Deploy so we can deploy: • Web Services • Windows services • Desktop applications WINDOWS.
41. OCTOPUS DEPLOY. Pushing packages to servers.
42. BUILD STEP 3. Publish to test environment.
43. ACHIEVEMENT. Continuous delivery.
44. BUILD STEP 4. Publish to acceptance environment.
45. BUILD STEP 5. Publish to production environment.
46. ACHIEVEMENT. Continuous deployment.
47. ACHIEVEMENT. Continuous deployment.
48. CONTINUOUS. delivery vs deployment
49. • Automated inspection • Automated delivery • Except production • May have automated post deployment tests Every change is proven to be deployable!
 Deployment after manual trigger CONTINUOUS DELIVERY.
50. • Continuous delivery • Automated deployment to production • Has automated post-deploy tests CONTINUOUS DEPLOYMENT.
51. POST-DEPLOY Tests
52. • Website still up? • Does the functionality work? • New functionality • Old functionality • especially old functionality (regression) • Haven’t I killed the infrastructure? CHECK FOR SUCCESS.
53. AUTOMATE SMOKE TESTS. Validate essentials are correct.
54. MONITORING. Monitor infrastructure state.
55. APPLICATION STATISTICS. Measure everything. give you up let you down run you down & desert you make you cry say goodbye tell a lie & hurt you
56. HEARTBEAT Is your application still alive?
57. FUNCTIONAL TESTS. Automated regression testing.
58. APPROACHES automated deployment
59. DEPLOY & REVERT. Revert in case of problems.
60. PRE-DEPLOYMENT TESTS. Run post-deploy test on acceptance environment.
61. CANARY DEPLOYMENT. Deploy to part of a cluster and test in production.
62. • Deploy to part of the cluster • X% percentage live • A/B testing (?) CANARY DEPLOYMENT.
63. ACHIEVEMENT. Continuous deployment.
64. DEVELOP, TEST, DEPLOY, REPEAT. Review & test Write code Commit & push Open pull request Build Package Staging Production Post-deploy tests Post-deploy
 tests
65. PROBLEM / CHALLENGE. Reverting data/data structures.
66. NUTS. Are you.
67. NO TESTERS NO QUARANTINE
 NO 1000+ PAGE TEST SCRIPT NO SIGN-OFF
68. TAKING RISKS. What suits your comfort zone.
69. GATHER LEARNINGS FAST. By releasing often and quick.
70. WAIT A MINUTE What do you actually have in place
71. • Automated smoke tests on acceptance environment • User acceptance tests (AKA The PO test) POST-DEPLOY TESTS @ COOLBLUE.
72. REVIEWING OUR BUILD PIPELINE. Build steps in our continuous delivery currently.
73. TESTING DEPLOY & REVERT A few services have continuous deployment as a test.
74. CANARY DEPLOYMENT. Feature switches for the win.
75. CONTINUOUS DELIVERY.
76. FEEDBACK. You got something to say.
77. • p.deraaij@coolblue.nl • @pderaaij • http://slideshare.net/pderaaij • http://devblog.coolblue.nl/ • http://careersatcoolblue.com/ THANK YOU.