CI/CD

Continuous Delivery and Continuous Deployment

Separate continuous delivery from continuous deployment by keeping software deployable on demand and making production release policy an explicit decision.

Intermediate14 min read
CI/CD lessonDelivery and reliability foundationsPractice

UNTIMED COACHING

Practice before the pressure

Use feedback to correct the model, not merely memorize an option position.

GUIDED PRACTICE

Practice the lesson questions

Answer normal lesson questions without a timer. Every answer includes an explanation, and incorrect answers can be tried again before continuing.

CONCEPT MODELS

See the lesson as a system

Use these visual guides to connect the key ideas before answering the questions.

Connect the roles in Continuous Delivery and Continuous DeploymentKeep delivery candidate, release policy, deployment process, and continuous deployment as separate service roles.
Connect the roles in Continuous Delivery and Continuous DeploymentA topic-specific model connects four distinct roles used to reason about continuous delivery and continuous deployment.
Candidate packagePackage remains deployable after every change
Release decisionDecision chooses when users receive change
Deployment processProcess promotes one verified package
Automated deploymentProcess releases qualifying changes
Verify Service verificationConnect service verification with its topic-specific inspection, expected outcome, and protected delivery boundary.
Verify Service verificationA verification model for continuous delivery and continuous deployment connects the final service decision to its check, result, and protected boundary.
Output evidenceEvidence confirms live service behavior
Starting checkInspect output evidence
Expected resultConfirm output evidence
Safety boundaryProtect candidate package scope