Deploying 1000 times a day without a hassle

Continuous deployment multiple times a day can be a pain. It's all about getting comfortable with your deployments.

Transcript

1. DEPLOYING 1000 TIMES A DAY
 WITHOUT A HASSLE
2. Hans Dubois Webdeveloper Scrum master 3,5 years @ Coolblue @hansdubois
 h.dubois@coolblue.nl
3. DEPLOYING 1000 TIMES A DAY
 WITHOUT A HASSLE
4. BEING COMFORTABLE DEPLOYING
5. MY 5 MINUTES OF SHAME..
6. NOW IT’S YOUR TURN!
7. SVN/HG/GIT CHECKOUT IN PRODUCTION
8. COMPOSER INSTALL IN PRODUCTION
9. MAINTAIN A LIST OF CHANGES 
 AND FTP THIS TO PRODUCTION
10. MAINTAIN A LIST OF STEPS TO TAKE TO DEPLOY TO PRODUCTION
11. NOT DEPLOYING ON FRIDAYS
12. DEPLOYING 1000 TIMES A DAY
 WITHOUT A HASSLE
13. Continuous delivery is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time.
14. Continuous deployment is a software engineering approach in which teams produce software in short cycles, ensuring that the software will be reliably deployed when all checks have passed.
15. IT’S ALL ABOUT FEELING COMFORTABLE
16. SHORT CYCLES
17. WHICH ONE WOULD YOU RATHER FIGHT?
18. One horse sized duck (Phorusrhacid)
19. 100 duck sized horses (Eohippus)
20. PROGRESS
21. EARLY FEEDBACK
22. • Find out if your solution works • Monitor it’s effect • Detect bugs faster • Gather data • Act to change BENEFITS OF EARLY FEEDBACK
23. NOT DEPLOYING ON FRIDAYS
24. FAMILY TIME
25. NOT DEPLOYING ON FRIDAYS MEANS LOSING 3 DAYS 
 OF VALUABLE FEEDBACK
26. FAMILY TIME
27. RELIABILITY
28. IF YOUR CODE WAS A PLANE WOULD YOU GET ON IN?
29. • Unit • Integration • Acceptance • Behaviour • Smoke tests • Code coverage TESTS!
30. ALL CODE SHOULD BE TESTED
31. START TESTING TODAY!
32. ALL NEW CODE MUST BE TESTED
33. BUT WHAT ABOUT LEGACY?
34. Test all critical code
35. Feature: Filter on category
 As a visitor
 I want to narrow my search by filtering on category
 So that I can find the product I am looking for
 
 Scenario: Filter on category
 Given I have searched on the term 'canon'
 When I and filter on category 'printers'
 Then I should only see 'printers' matched with 'canon'
 
 Scenario: Reset category filter
 Given I have searched on the term 'canon'
 And I have selected the category 'printers'
 When I click 'Alle categorieën'
 Then I should only see 'Alle categorieën'
 
 Scenario: Having search query narrows facets
 Given I am on the search page
 When I search on the term 'canon'
 Then The only brand facet I should see is 'canon'
 
 Scenario: Selecting a filter narrows facets
 Given I am on the search page
 When I and filter on category 'printers'
 Then The brand facets I should see are 'canon' and 'hp'
 And Category filters remain unfiltered Feature example
36. this.When(/^I search on the term '(\w+)'$/, term => {
 return browser.url(this.World().createFullUrl('/?query=' + term));
 });
 
 this.Then(/^The only brand facet I should see is '(.*)'$/, brand => {
 const brandAttribute = browser.getAttribute('input[name="merk"]', 'value');
 
 expect(brandAttribute).toBe(brand);
 });
 
 this.Then(/^The brand facets I should see are 'canon' and 'hp'$/, () => {
 const brands = browser.getAttribute('input[name="merk"]', 'value');
 
 expect(brands.length).toBe(2);
 expect(brands[0]).toBe('hp');
 expect(brands[1]).toBe('canon');
 }); Magic behind Feature files
37. LINT ALL YOUR CODE!
38. BEHAVIOUR TEST YOUR LEGACY CODE
39. DEPLOYMENT
40. 1. Update code 2. Install dependencies (composer/npm etc.) 3. Precompile templates 4. Remove cache 5. Restart services Typical deployment
41. SCRIPT EVERY STEP!
42. TASK EVERY STEP!
43. Available tasks build Cleans and builds all assets and templates for production [build:js, build:sass, build:templates] build:js Bundle, transpile, version and minify the javascript code. [clean:js] build:js:watch Bundle, transpile, version and watch the javascript code. [clean:js] build:sass Compiles SASS to CSS [clean:css] build:sass:development Compiles SASS to CSS with sourcemaps [clean:css] build:sass:watch [build:sass:development] build:templates Pre-compiles the twig templates. clean:css Cleans up the css assets clean:js Cleans up the javascript assets install Install Composer and npm packages. install:development Install e-commerce locally for development. lint [lint:php, lint:js, lint:sass, lint:gherkin] lint:gherkin Check Gherking feature code. lint:js Check Javascript code using ESLint lint:php Check the code style using Code Sniffer (CS). lint:php:fix Automatically fix code style issues using the Code Beautifier and Fixer (CBF). lint:sass Check SASS code using Sass Lint pre-commit [lint, test:js:check-coverage, test:php:check-coverage, test:php:integration] test [test:php, test:js] test:acceptance Run all the acceptance tests using Chimp. [build, provision] test:acceptance:headless Run all the acceptance tests using Chimp and Phantomjs. [build, provision] test:acceptance:watch Watch the acceptance tests marked as watch. [build, provision] test:js Run javascript unit tests using ava. test:js:check-coverage Run javascript coverage and validate against the coverage thresholds. test:js:coverage Run javascript unit tests with code coverage reports using ava and nyc. test:js:watch Run javascript unit tests using ava. test:php Run all the tests using PHPUnit. [test:php:unit, test:php:integration] test:php:check-coverage Run the coverage and validate against the coverage thresholds. test:php:coverage Run all the unit tests with coverage using PHPUnit. test:php:integration Run all the integration tests using Phpunit. test:php:unit Run all the unit tests using PHPUnit. test:php:watch Continuously run all the tests using PHPUnit. [test:php] watch Watch javascript and sass assets [build:js:watch, build:sass:watch] All tasks at hand
44. HOW DO I RELEASE MY RISKY FEATURES
45. FEATURE SWITCHES
46. "Feature Toggling" is a set of patterns which can help a team to deliver new functionality to users rapidly but safely. http://martinfowler.com/articles/feature-toggles.html
47. QANDIDATE TOGGLE https://github.com/qandidate-labs/qandidate-toggle
48. $username = $order->getCustomerDetails()->getEmail();
 if (strpos($username, "coolblue.test") !== false) {
 // YOUR CODE HERE } The most simple feature switch ever
50. DEPLOY!
51. BOX IT!
52. • Easy distribution • No dependency install in production • Reusable • Environment independant PACKAGE DEPLOYMENT
53. • A basic CI tool can do it. • Travis • Codeship • Scrutinizer • Jenkins • etc. BOXING IT
54. SHIP IT!
55. • A basic CI tool can do it. • Ship to S3 • Push to rpm repo • 1000 other ways to ship it SHIPPING IT
56. SHIP IT!
62. LEARN FROM YOUR MISTAKES
63. CREATE THE TEST CASE SO IT DOES NOT HAPPEN AGAIN
64. DEPLOYMENTS AT COOLBLUE
65. TRUNK BASED DEVELOPMENT
66. EVERY DEVELOPER CAN MERGE A PULL REQUEST
67. TAILOR MADE DEPLOYMENT STRATEGY FOR EACH PROJECT
70. WHERE DO I START?!
74. IT’S ALL ABOUT FEELING COMFORTABLE
75. TAKING THE RISKS INTO ACCOUNT
76. HAVING THE RIGHT STRATEGY
77. FEATURE SWITCHING