I deploy on Fridays (and maybe you should too) (ConFoo 2019)

I deploy on Fridays (and maybe you should too) (ConFoo 2019)

Have you ever heard someone say “Don’t deploy on Friday”? I used to say that too!
Join me as I'll tell you about my experience. Using examples from my work on multiple real world projects, I’ll discuss resilience and operability, deployment strategies, pipelines and continuous testing. Discover the details of trunk based development, feature toggles, pair programming and other best practices and gain the confidence to deploy any day of the week!

2f4800411154a8c66dde489448a044d2?s=128

Michiel Rook

March 13, 2019
Tweet

Transcript

  1. 6.
  2. 7.
  3. 8.
  4. 9.
  5. 57.
  6. 68.

    @michieltcs "This pull request affects 31 files...
 could be a

    lot of conflicts if we don't merge it soon"
  7. 102.

    @michieltcs CONTINUOUS TESTING UNIT TESTS ACCEPTANCE TESTS E2E
 TESTS Cost

    Speed Exploratory
 testing & user
 feedback Monitoring
 & alerting INTEGRATION TESTS
  8. 116.

    @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