Continuous delivery and deployment
Environments and the promotion of one artifact, continuous delivery versus continuous deployment, per-environment configuration, compatible database migrations, rollback and the four DORA metrics.
- 23 cards
- 5 topics
- Free
The outline, topic by topic
Each topic is weighted the way the exam weighs it.
- Concepts
- Questions
- Sort and link
- The numbers
- Scenarios
A few cards from the deck
Continuous delivery: what is it?
Show the answer
A practice where every validated change yields an artifact ready to go to production at any time, the decision to send it there remaining human.
Automation goes up to production's door; a manual approval click triggers the final stage.
In this pipeline, what must change to go from continuous delivery to continuous deployment?
```yaml
stages: [build, test, staging, production]
deploy-staging:
stage: staging
script: [./deploy.sh staging]
deploy-production:
stage: production
script: [./deploy.sh production]
when: manual`- Remove
when: manualfrom the production job - Add
when: manualto the staging job - Remove the staging stage
- Replace
deploy.shwith a progressive deployment
Show the answer
Remove
when: manualfrom the production jobwhen: manualrequires a human click before production: that is continuous delivery. Without it, every change that passes the previous stages goes by itself: that is continuous deployment.- Remove
The … is the share of production releases that require an urgent fix or a rollback.
Show the answer
The change failure rate is the share of production releases that require an urgent fix or a rollback.
It is computed on releases and not on commits: 3 releases to remediate out of 60 gives 5%.
Continuous deployment: what is it?
Show the answer
A practice where every change that passes all automated checks goes to production with no human intervention.
It assumes trustworthy tests and monitoring: only the quality of the pipeline protects production, since nobody approves by hand any more.