I deploy on Fridays (and maybe you should too)

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

@michieltcs

@michieltcs DEPLOYING

@michieltcs ON A FRIDAY

@michieltcs

@michieltcs DEPLOYING?

@michieltcs ON A  FRIDAY??

@michieltcs

@michieltcs BUT WHY?

@michieltcs TRADITION

@michieltcs RISK

@michieltcs CONTROL

@michieltcs CONFIDENCE & TRUST

@michieltcs TIME TO REPAIR / RECOVER

@michieltcs ON-CALL

@michieltcs SO

@michieltcs DON'T DEPLOY ON A FRIDAY!

@michieltcs I USED TO SAY THAT TOO

@michieltcs I LIKE MY WEEKENDS

@michieltcs AND MY EVENINGS

@michieltcs WHAT ABOUT BUGS?

@michieltcs WHAT ABOUT 3 PM?

@michieltcs WHAT ABOUT THURSDAY?

@michieltcs FRIDAY IS 20%  OF THE WEEK

@michieltcs IMPROVE!

@michieltcs IF IT HURTS  DO IT MORE OFTEN

@michieltcs FAILURE IS NOT  THE OPPOSITE OF SUCCESS

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

@michieltcs BIG STEPS

@michieltcs FAIL BIG

@michieltcs SMALL STEPS

@michieltcs FAIL SMALL

@michieltcs MAKE IT EFFORTLESS

@michieltcs REDUCE RISK

@michieltcs $ = REALIZED VALUE  CREDITS TO @FGOULDING

@michieltcs CONTINUOUS EVERYTHING

@michieltcs DELIVERING VALUE TO USERS

@michieltcs SAFELY & QUICKLY

@michieltcs IN A SUSTAINABLE WAY

@michieltcs DEV BUILD / TEST ACCEPTANCE PRODUCTION CONTINUOUS DELIVERY

@michieltcs CODE IS ALWAYS  IN A RELEASABLE STATE

@michieltcs DEV BUILD / TEST ACCEPTANCE PRODUCTION CONTINUOUS DEPLOYMENT

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

@michieltcs SO

@michieltcs IF YOU CAN DEPLOY  ON FRIDAY

@michieltcs AT 5 PM

@michieltcs YOU CAN DEPLOY  ANY TIME

@michieltcs BUT OUR CODE IS OLD

@michieltcs BUT OUR CODE IS NOT UNDER TEST

@michieltcs BUT OUR CODE IS IMPOSSIBLE TO CHANGE

@michieltcs DEALING WITH "LEGACY"

@michieltcs STRANGLER PATTERN

@michieltcs ORIGINAL MONOLITH DB @michieltcs

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

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

@michieltcs BRANCH BY ABSTRACTION

@michieltcs CLIENT OLD MODULE CLIENT CLIENT @michieltcs

@michieltcs CLIENT ABSTRACTION LAYER OLD MODULE CLIENT CLIENT @michieltcs

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

@michieltcs CLIENT ABSTRACTION LAYER CLIENT CLIENT NEW MODULE @michieltcs

@michieltcs CLIENT NEW MODULE CLIENT CLIENT @michieltcs

@michieltcs ON BRANCHES

@michieltcs CONFLICTS

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

@michieltcs

@michieltcs CONTINUOUS INTEGRATION

@michieltcs INTEGRATE TO MASTER  AT LEAST DAILY

@michieltcs DELAYING INTEGRATION

@michieltcs MERGING FEATURES?

@michieltcs DECOUPLE  DEPLOYMENTS FROM RELEASES

@michieltcs FEATURE TOGGLES

@michieltcs

@michieltcs @michieltcs

@michieltcs FEATURE TOGGLE DEBT

@michieltcs BRANCHING STRATEGIES

@michieltcs BRANCHING STRATEGIES 1. DON'T BRANCH

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

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

@michieltcs

@michieltcs TRUNK  BASED DEVELOPMENT

@michieltcs SHORT LIVED  FEATURE BRANCHES?

@michieltcs PULL REQUESTS?

@michieltcs CODE REVIEWS ARE USEFUL

@michieltcs BUT: FLOW DELAY

PAIR PROGRAMMING

@michieltcs CONTINUOUS INLINE  CODE REVIEW

MOB PROGRAMMING

@michieltcs PIPELINES

@michieltcs AUTOMATION

@michieltcs AUTOMATION  AUTOMATION

@michieltcs AUTOMATION  AUTOMATION  AUTOMATION

@michieltcs COMPILE CHECKOUT TEST PACKAGE

@michieltcs DEPLOY ACC VERIFY ACC DEPLOY PROD VERIFY PROD

@michieltcs CONTINUOUS TESTING

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

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

@michieltcs GOOD ENOUGH

@michieltcs NO TEST SUITE DETECTS EVERY ISSUE

@michieltcs PIPELINE SPEED = KEY

@michieltcs DEPLOYMENTS

@michieltcs ROLLING UPDATE

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

V1.0 SERVICE V1.1 @michieltcs

V1.1 @michieltcs

@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

@michieltcs BUILD PIPELINE @michieltcs

@michieltcs FEEDBACK!

@michieltcs DEPLOYING

@michieltcs ON A FRIDAY

@michieltcs YOU CAN DO IT TOO!

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

I deploy on Fridays (and maybe you should too)

I deploy on Fridays (and maybe you should too)

More Decks by Michiel Rook

Other Decks in Programming

Featured

Transcript