FreeLevel 3 · Professional

CI/CD and Containers

In June 2026, Tallybook replaced deployments by hand with a container pipeline. In this course you take that pipeline apart and measure what it changed. You'll calculate the four DORA measures before and after, read Tallybook's original Dockerfile and write a checker that finds its six problems (including the production database password baked into the image), compare base images by size, build time and vulnerability scans, and load the old GitHub Actions workflow as data to find the six gaps that let any branch deploy to production with a third-party action holding the deploy key. Then you'll measure where pipeline time goes and what caching saved, test the canary rule against every release since June, and compare rolling back with fixing forward. Every number comes from running the code on the course's data.

About 7 hours
10 modules
1 badge
Final project
Optional verified certificate

Curriculum

01Why CI/CDWhat continuous integration and continuous delivery are, the four DORA measures of software delivery, and how they changed when Tallybook replaced manual deployments with a pipeline.15 min
02Containers and ImagesWhat containers and images are and why pipelines build them, how a Dockerfile's instructions become image layers, and what the choice of base image does to size and build time.15 min
03Better DockerfilesCheck a Dockerfile against the rules that matter (pinned base images, cache-friendly order, no secrets, a non-root user, small runtime images) with a small linter you write yourself, then rewrite Tallybook's as a multi-stage build.25 min
04Image VulnerabilitiesRead container vulnerability scan reports, separate problems in the base image from problems in your own dependencies, and set a scanning rule the pipeline can enforce without blocking every release.25 min
05Pipelines as CodeRead a CI/CD pipeline defined in YAML (triggers, jobs, steps, dependencies and secrets), load it as data, and map how Tallybook's old GitHub Actions workflow actually ran.15 min
06Securing the PipelineReview a deployment pipeline for the mistakes that let untested or malicious code reach production (broad triggers, missing dependencies, excessive permissions, unpinned third-party actions and leaked secrets), and write the fixed workflow.25 min
07Faster PipelinesMeasure where a pipeline's time goes, step by step, see what dependency and image-layer caching saved, and find what to speed up next.15 min
08Canary ReleasesCompare deployment strategies (all at once, rolling, blue-green and canary), analyse canary checks that compare a new version's errors with the old one's, and tune the rule that decides whether to promote or roll back.25 min
09Rollbacks and RecoveryCompare rolling back with fixing forward, measure time to restore under the old and new processes, and design releases (feature flags, backwards-compatible changes) that make recovery fast.20 min
10Final ProjectPlan your final project, a review of how Tallybook builds, secures and releases software, with DORA measures, fixed Dockerfile and workflow, scanning and canary policies, and the next improvements.20 min
Final assessmentPass it (60% or more) to earn the CI/CD and Containers course completion badge.

Loading…

CI/CD and Containers

About 7 hours

10 modules

1 badge

Final project

Optional verified certificate

Curriculum

01Why CI/CDWhat continuous integration and continuous delivery are, the four DORA measures of software delivery, and how they changed when Tallybook replaced manual deployments with a pipeline.15 min

02Containers and ImagesWhat containers and images are and why pipelines build them, how a Dockerfile's instructions become image layers, and what the choice of base image does to size and build time.15 min

03Better DockerfilesCheck a Dockerfile against the rules that matter (pinned base images, cache-friendly order, no secrets, a non-root user, small runtime images) with a small linter you write yourself, then rewrite Tallybook's as a multi-stage build.25 min

04Image VulnerabilitiesRead container vulnerability scan reports, separate problems in the base image from problems in your own dependencies, and set a scanning rule the pipeline can enforce without blocking every release.25 min

05Pipelines as CodeRead a CI/CD pipeline defined in YAML (triggers, jobs, steps, dependencies and secrets), load it as data, and map how Tallybook's old GitHub Actions workflow actually ran.15 min

06Securing the PipelineReview a deployment pipeline for the mistakes that let untested or malicious code reach production (broad triggers, missing dependencies, excessive permissions, unpinned third-party actions and leaked secrets), and write the fixed workflow.25 min

07Faster PipelinesMeasure where a pipeline's time goes, step by step, see what dependency and image-layer caching saved, and find what to speed up next.15 min

08Canary ReleasesCompare deployment strategies (all at once, rolling, blue-green and canary), analyse canary checks that compare a new version's errors with the old one's, and tune the rule that decides whether to promote or roll back.25 min

09Rollbacks and RecoveryCompare rolling back with fixing forward, measure time to restore under the old and new processes, and design releases (feature flags, backwards-compatible changes) that make recovery fast.20 min

10Final ProjectPlan your final project, a review of how Tallybook builds, secures and releases software, with DORA measures, fixed Dockerfile and workflow, scanning and canary policies, and the next improvements.20 min

Final assessmentPass it (60% or more) to earn the CI/CD and Containers course completion badge.