1. CONTINUOUS DELIVERY
„WHETHER YOU THINK YOU CAN, OR YOU THINK YOU CAN’T… YOU’RE RIGHT”
BY HENRY FORD

2. WHO AM I?
• Quality software engineer
• Working in Kanban team (4 +5 people)
• Working on a middleware project
integrating banking front office with
backend systems

3. AGENDA
• Terminology – continuous integration/delivery/deployment
• Why should you care?
• Prerequisites
• Implementation
• Beware of pipeline dependencies
• Continuous deployment aka Zero down time deployment

4. CONTINUOUS…
• … Integration
• Merge changes to master/trunk at least daily
• You cannot merge to master/trunk if your code does not compile
• … Delivery
• Merge changes to master/trunk only if complete set of tests passed
• Make sure that you feel comfortable with deploying the artefact that
passed CD pipeline
• … Deployment
• Deploy to production at least daily

5. REALITY
• Continuously red night-builds
• Continuous analysis of the build result
• Continuous chasing for the guilty
• Continuous feeling of being a trouble-
maker
• Continuous manual regression
• Hardening iterations
• Continuous Delivery/Deployment

6. ENABLING "THE CONTINUOUS"
"DON'T DEMAND PERFECTION BUT INSIST ON
CONTINUOUS IMPROVEMENT" BY ANONYMOUS
• Scripts used to build environment
• Scripts used to build application
• Scripts used to deploy application
• Unit/Integration/System/Performance tests

7. PIPELINE HIGH LEVEL
PullReq Triggers Builds

8. Delivery Pipeline Plugin

10. PIPELINE DEPENDENCIES
• Upstream pipelines trigger downstream
• Dependency classification
• Static
• Fluid
• Guarded

11. ZERO DOWNTIME
• Blue-green deployment

12. ZERO DOWNTIME
• Blue-green deployment
• Canary deployment
• A bit more about „how”?
• „Expand and contract” pattern
• Non breakable changes

14. THANK YOU
REMIGIUSZ DUDEK