CI/CD Fundamentals

By the end

What you'll build

• Design a branching and integration approach and explain its effect on delivery speed and risk
• Write pipeline configuration as reviewable code with shared templates
• Decide which tests run on every commit and which run on a slower cadence, and defend the split
• Promote one immutable artefact through environments with traceable provenance
• Choose between rolling, blue-green and canary deployment for a given service and define rollback criteria
• Instrument a pipeline to show lead time, queue time and failure signals

Curriculum

What's inside

7 modules · 35 lessons

1. 01

   Continuous integration

   5 lessons
   • What integrated really means, and why trunk health is the goal
   • Branching models and their delivery cost
   • Build reproducibility and caching
   • Fast feedback and keeping the build short
   • Integrated, or just greenmatch pairs
2. 02

   Pipelines as code

   5 lessons
   • Designing a pipeline that is still readable a year later
   • Stages, jobs and dependency graphs
   • Shared pipeline libraries and templates
   • Reviewing pipeline changes like production code
   • Pipelines people can still readfill blank
3. 03

   Testing in the pipeline

   5 lessons
   • Deciding what runs on every commit and what runs overnight
   • Test selection and quarantining flaky tests
   • Quality gates that do not become theatre
   • Test data and environment strategy
   • Handling a test that failed for no reasonsequence order
4. 04

   Artefacts and the supply chain

   5 lessons
   • Build once, promote everywhere: artefact promotion in practice
   • Versioning, immutability and provenance
   • Dependency management and vulnerability gates
   • Signing and verification in outline
   • The hotfix that had to ship by Fridayscenario
5. 05

   Deployment strategies

   5 lessons
   • Choosing between rolling, blue-green and canary for a given service
   • Feature flags and separating release from deploy
   • Automated rollback criteria
   • Database change and deployment ordering
   • Match the deployment mechanism to the job it doesmatch pairs
6. 06

   Measuring delivery

   5 lessons
   • Instrumenting a pipeline to see where change waits
   • Lead time, deployment frequency and failure signals
   • Queue time and pipeline reliability
   • Improvement work driven by pipeline evidence
   • Say what you measuredfill blank
7. 07

   Practice and check

   5 lessons
   • Symptom and cause in a delivery pipelinematch pairs
   • Getting one change into production without rebuilding itsequence order
   • The vocabulary people get wrongfill blank
   • A one-line fix and a red trunkscenario
   • Course quizquiz

The shape of it

How this course works