Slide 1

Slide 1 text

I DEPLOY ON
 FRIDAYS
 (AND MAYBE YOU SHOULD TOO) MICHIEL ROOK
 @MICHIELTCS

Slide 2

Slide 2 text

@michieltcs DEPLOYING

Slide 3

Slide 3 text

@michieltcs ON A FRIDAY

Slide 4

Slide 4 text

@michieltcs DEPLOYING?

Slide 5

Slide 5 text

@michieltcs ON A
 FRIDAY??

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

@michieltcs

Slide 11

Slide 11 text

@michieltcs BUT WHY?

Slide 12

Slide 12 text

@michieltcs TRADITION

Slide 13

Slide 13 text

@michieltcs RISK

Slide 14

Slide 14 text

@michieltcs CONTROL

Slide 15

Slide 15 text

@michieltcs CONFIDENCE & TRUST

Slide 16

Slide 16 text

@michieltcs TIME TO REPAIR / RECOVER

Slide 17

Slide 17 text

@michieltcs ON-CALL

Slide 18

Slide 18 text

@michieltcs SO

Slide 19

Slide 19 text

@michieltcs DON'T DEPLOY ON A FRIDAY!

Slide 20

Slide 20 text

@michieltcs I USED TO SAY THAT TOO

Slide 21

Slide 21 text

@michieltcs I LIKE MY WEEKENDS

Slide 22

Slide 22 text

@michieltcs AND MY EVENINGS

Slide 23

Slide 23 text

@michieltcs WHAT ABOUT BUGS?

Slide 24

Slide 24 text

@michieltcs WHAT ABOUT 3 PM?

Slide 25

Slide 25 text

@michieltcs WHAT ABOUT THURSDAY?

Slide 26

Slide 26 text

@michieltcs FRIDAY IS 20%
 OF THE WEEK

Slide 27

Slide 27 text

@michieltcs IMPROVE!

Slide 28

Slide 28 text

@michieltcs IF IT HURTS
 DO IT MORE OFTEN

Slide 29

Slide 29 text

@michieltcs FAILURE IS NOT
 THE OPPOSITE OF SUCCESS

Slide 30

Slide 30 text

SUCCESS CONSISTS OF GOING FROM FAILURE TO FAILURE WITHOUT LOSS OF ENTHUSIASM. Winston Churchill

Slide 31

Slide 31 text

@michieltcs BIG STEPS

Slide 32

Slide 32 text

@michieltcs FAIL BIG

Slide 33

Slide 33 text

@michieltcs SMALL STEPS

Slide 34

Slide 34 text

@michieltcs FAIL SMALL

Slide 35

Slide 35 text

@michieltcs MAKE IT EFFORTLESS

Slide 36

Slide 36 text

@michieltcs REDUCE RISK

Slide 37

Slide 37 text

@michieltcs $ = REALIZED VALUE
 CREDITS TO @FGOULDING

Slide 38

Slide 38 text

@michieltcs CONTINUOUS EVERYTHING

Slide 39

Slide 39 text

@michieltcs DELIVERING VALUE TO USERS

Slide 40

Slide 40 text

@michieltcs SAFELY & QUICKLY

Slide 41

Slide 41 text

@michieltcs IN A SUSTAINABLE WAY

Slide 42

Slide 42 text

@michieltcs DEV BUILD / TEST ACCEPTANCE PRODUCTION CONTINUOUS DELIVERY

Slide 43

Slide 43 text

@michieltcs CODE IS ALWAYS
 IN A RELEASABLE STATE

Slide 44

Slide 44 text

@michieltcs DEV BUILD / TEST ACCEPTANCE PRODUCTION CONTINUOUS DEPLOYMENT

Slide 45

Slide 45 text

@michieltcs HIGH VS. LOW PERFORMING TEAMS Source: Accelerate - The Science Of DevOps

Slide 46

Slide 46 text

@michieltcs SO

Slide 47

Slide 47 text

@michieltcs IF YOU CAN DEPLOY
 ON FRIDAY

Slide 48

Slide 48 text

@michieltcs AT 5 PM

Slide 49

Slide 49 text

@michieltcs YOU CAN DEPLOY
 ANY TIME

Slide 50

Slide 50 text

@michieltcs BUT OUR CODE IS OLD

Slide 51

Slide 51 text

@michieltcs BUT OUR CODE IS NOT UNDER TEST

Slide 52

Slide 52 text

@michieltcs BUT OUR CODE IS IMPOSSIBLE TO CHANGE

Slide 53

Slide 53 text

@michieltcs DEALING WITH "LEGACY"

Slide 54

Slide 54 text

@michieltcs STRANGLER PATTERN

Slide 55

Slide 55 text

@michieltcs ORIGINAL MONOLITH DB @michieltcs

Slide 56

Slide 56 text

@michieltcs ORIGINAL MONOLITH PROXY SERVICE ORIGINAL MONOLITH DB DB DB @michieltcs

Slide 57

Slide 57 text

@michieltcs ORIGINAL MONOLITH PROXY SERVICE ORIGINAL MONOLITH ORIGINAL MONOLITH SERVICE SERVICE SERVICE PROXY DB DB DB DB DB DB @michieltcs

Slide 58

Slide 58 text

@michieltcs BRANCH BY ABSTRACTION

Slide 59

Slide 59 text

@michieltcs CLIENT OLD MODULE CLIENT CLIENT @michieltcs

Slide 60

Slide 60 text

@michieltcs CLIENT ABSTRACTION LAYER OLD MODULE CLIENT CLIENT @michieltcs

Slide 61

Slide 61 text

@michieltcs CLIENT ABSTRACTION LAYER OLD MODULE CLIENT CLIENT @michieltcs

Slide 62

Slide 62 text

@michieltcs CLIENT ABSTRACTION LAYER OLD MODULE CLIENT CLIENT ABSTRACTION LAYER NEW MODULE @michieltcs

Slide 63

Slide 63 text

@michieltcs CLIENT ABSTRACTION LAYER OLD MODULE CLIENT CLIENT ABSTRACTION LAYER NEW MODULE @michieltcs

Slide 64

Slide 64 text

@michieltcs CLIENT ABSTRACTION LAYER CLIENT CLIENT NEW MODULE @michieltcs

Slide 65

Slide 65 text

@michieltcs CLIENT NEW MODULE CLIENT CLIENT @michieltcs

Slide 66

Slide 66 text

@michieltcs ON BRANCHES

Slide 67

Slide 67 text

@michieltcs CONFLICTS

Slide 68

Slide 68 text

@michieltcs "This pull request affects 31 files...
 could be a lot of conflicts if we don't merge it soon"

Slide 69

Slide 69 text

@michieltcs

Slide 70

Slide 70 text

@michieltcs CONTINUOUS INTEGRATION

Slide 71

Slide 71 text

@michieltcs INTEGRATE TO MASTER
 AT LEAST DAILY

Slide 72

Slide 72 text

@michieltcs DELAYING INTEGRATION

Slide 73

Slide 73 text

@michieltcs BRANCHING STRATEGIES

Slide 74

Slide 74 text

@michieltcs BRANCHING STRATEGIES 1. DON'T BRANCH

Slide 75

Slide 75 text

@michieltcs BRANCHING STRATEGIES 1. DON'T BRANCH 2. DON'T BRANCH

Slide 76

Slide 76 text

@michieltcs BRANCHING STRATEGIES 1. DON'T BRANCH 2. DON'T BRANCH 3. DON'T BRANCH

Slide 77

Slide 77 text

@michieltcs

Slide 78

Slide 78 text

@michieltcs TRUNK
 BASED DEVELOPMENT

Slide 79

Slide 79 text

@michieltcs ONLY COMMIT TO MASTER

Slide 80

Slide 80 text

@michieltcs MERGING FEATURES?

Slide 81

Slide 81 text

@michieltcs DECOUPLE
 DEPLOYMENTS FROM RELEASES

Slide 82

Slide 82 text

@michieltcs FEATURE TOGGLES

Slide 83

Slide 83 text

@michieltcs

Slide 84

Slide 84 text

@michieltcs @michieltcs

Slide 85

Slide 85 text

@michieltcs FEATURE TOGGLE DEBT

Slide 86

Slide 86 text

@michieltcs SHORT LIVED
 FEATURE BRANCHES?

Slide 87

Slide 87 text

@michieltcs PULL REQUESTS?

Slide 88

Slide 88 text

@michieltcs CODE REVIEWS ARE USEFUL

Slide 89

Slide 89 text

@michieltcs BUT: FLOW DELAY

Slide 90

Slide 90 text

PAIR PROGRAMMING

Slide 91

Slide 91 text

@michieltcs CONTINUOUS INLINE
 CODE REVIEW

Slide 92

Slide 92 text

MOB PROGRAMMING

Slide 93

Slide 93 text

@michieltcs PIPELINES

Slide 94

Slide 94 text

@michieltcs AUTOMATION

Slide 95

Slide 95 text

@michieltcs AUTOMATION
 AUTOMATION

Slide 96

Slide 96 text

@michieltcs AUTOMATION
 AUTOMATION
 AUTOMATION

Slide 97

Slide 97 text

@michieltcs COMPILE CHECKOUT TEST PACKAGE

Slide 98

Slide 98 text

@michieltcs DEPLOY ACC VERIFY ACC DEPLOY PROD VERIFY PROD

Slide 99

Slide 99 text

@michieltcs CONTINUOUS EVERYTHING

Slide 100

Slide 100 text

@michieltcs CONTINUOUS TESTING

Slide 101

Slide 101 text

@michieltcs CONTINUOUS TESTING UNIT TESTS ACCEPTANCE TESTS E2E
 TESTS Cost Speed INTEGRATION TESTS

Slide 102

Slide 102 text

@michieltcs CONTINUOUS TESTING UNIT TESTS ACCEPTANCE TESTS E2E
 TESTS Cost Speed Exploratory
 testing & user
 feedback Monitoring
 & alerting INTEGRATION TESTS

Slide 103

Slide 103 text

@michieltcs GOOD ENOUGH

Slide 104

Slide 104 text

@michieltcs NO TEST SUITE DETECTS EVERY ISSUE

Slide 105

Slide 105 text

@michieltcs PIPELINE SPEED = KEY

Slide 106

Slide 106 text

@michieltcs DEPLOYMENTS

Slide 107

Slide 107 text

@michieltcs ROLLING UPDATE

Slide 108

Slide 108 text

@michieltcs LOAD BALANCER ROLLING UPDATE SERVICE V1.0 SERVICE V1.0 SERVICE V1.0 @michieltcs

Slide 109

Slide 109 text

@michieltcs LOAD BALANCER ROLLING UPDATE SERVICE V1.0 SERVICE V1.0 SERVICE V1.0 SERVICE V1.1 @michieltcs

Slide 110

Slide 110 text

@michieltcs LOAD BALANCER ROLLING UPDATE SERVICE V1.0 SERVICE V1.1 SERVICE V1.0 SERVICE V1.0 @michieltcs

Slide 111

Slide 111 text

@michieltcs LOAD BALANCER ROLLING UPDATE SERVICE V1.0 SERVICE V1.1 SERVICE V1.0 SERVICE V1.1 @michieltcs

Slide 112

Slide 112 text

@michieltcs LOAD BALANCER ROLLING UPDATE SERVICE V1.0 SERVICE V1.1 SERVICE V1.1 SERVICE V1.0 @michieltcs

Slide 113

Slide 113 text

@michieltcs LOAD BALANCER ROLLING UPDATE SERVICE V1.0 SERVICE V1.1 SERVICE V1.1 SERVICE V1.1 @michieltcs

Slide 114

Slide 114 text

@michieltcs LOAD BALANCER ROLLING UPDATE SERVICE V1.1 SERVICE V1.1 SERVICE V1.1 SERVICE V1.0 @michieltcs

Slide 115

Slide 115 text

@michieltcs LOAD BALANCER ROLLING UPDATE SERVICE V1.1 SERVICE V1.1 SERVICE V1.1 @michieltcs

Slide 116

Slide 116 text

@michieltcs pipeline {
 stages {
 stage('Run tests') {
 sh "gradle check"
 }
 
 stage('Build docker image') {
 sh "docker build -t jobservice:${env.BUILD_NUMBER} ."
 sh "docker push jobservice:${env.BUILD_NUMBER}"
 }
 
 stage('Deploy staging') {
 sh "ansible-playbook -e BUILD=${env.BUILD_NUMBER}
 -i staging deploy.yml"
 }
 
 stage('Deploy production') {
 sh "ansible-playbook -e BUILD=${env.BUILD_NUMBER}
 -i prod deploy.yml"
 }
 }
 PIPELINE AS CODE image: registry.local/runner:latest
 
 stages:
 - test
 - images
 - deploy
 
 phpunit:
 stage: test
 script:
 - bin/phpunit
 
 images:
 stage: images
 script:
 - make images publish
 only:
 - master
 
 deploy:
 stage: deploy
 script:
 - make deploy
 only:
 - master

Slide 117

Slide 117 text

@michieltcs BUILD PIPELINE @michieltcs

Slide 118

Slide 118 text

@michieltcs FEEDBACK!

Slide 119

Slide 119 text

@michieltcs DEPLOYING

Slide 120

Slide 120 text

@michieltcs ON A FRIDAY

Slide 121

Slide 121 text

@michieltcs YOU CAN DO IT TOO!

Slide 122

Slide 122 text

@michieltcs THANK YOU FOR LISTENING! @michieltcs / [email protected] www.michielrook.nl