continuous delivery is not finished

Continuous delivery is not finished?!

Hylke Stapersma | Software CraftsmanMiel Donkers | Software CraftsmanTraining – Coaching – Consultancy – Audits – Project Management

Introduction1. Short introduction continuous delivery2. Why not finished?3. Pipeline as code4. Monitoring and mitigation5. Experimentation6. Conclusions / final thoughts / Vision7. Questions

Automated Pipeline

CONTINUOUS DELIVERY - DEPLOYMENT PIPELINE

Release

Every change results in a trigger of the deployment process

Software is build once and only once

The same deployment process for every environment

Deployment in production-like environments

Commit Automated Acceptance

Test

Automated Capacity Test

ManualTesting

Fast Feedback

Trust in Application Stability

Done

Striving for- Consistent repeatable process- Quality built in- Fast feedback- Small steps- Flexibility

Why are we not finished?!

Only Production Counts!

Unexpected things happen

Testing filters out lots of issues

Real use brings up different issues

Neglected Principles

Neglected principles- Pipeline as software (pipeline versioning)- Monitoring / problem mitigation- Feedback to the business / Experimentation

Pipeline as code- Rebuild your pipeline as rebuilding your code- Versioning your pipeline- Reduce manual steps- Configuration as code

Evolution

Demo

Monitoring and mitigation- See- Act- Know

Sensors

Codahale Metrics library

Semantic Monitoring

Risk Assessment

Act

OTA Updates

01.05.2023 29

Dashboards

Experimentation / Exploration

Idea

Experiment

Why experiment?

Experimentation with continuous delivery

Sample experiment

Experiment: Decrease failed logins

Hypothesis: Showing caps-locks warning decreases failed logins by 5 procent within 2 weeks

Code

Experiment

Control

CD pipeline

Production

Lab

Trigger pipeline with new experiment

Lab triggers pipeline to integrate experiment into control

Deploy

Vision on continuous delivery- Every development / operations team should strive to do

continuous delivery- Continuous delivery plans, does, checks and acts on quality

and consistency- DevOps is the vehicle to do Continuous Delivery and vice-

versa- Everything should be code

Questions?