Prove the change can integrate
Commit ↓ Build ↓ Tests + quality gates
Fast automated feedback protects the shared codebase.
DevOps · Continuous integration · Continuous delivery
CI/CD Fundamentals
Build a delivery system from first principles: source change, pipeline-as-code, runners, reproducible builds, quality gates, artifacts, secure identity, controlled environments, container release evidence, health verification and rollback. The course contains 12 complete modules, a guided lab in every module, an end-to-end release capstone and a 35-minute randomized assessment.
My Learning progress
0% complete
0 of 12 curriculum modules completed · 0/12 currently published modules complete · 0 with lab + knowledge-check evidence.
Delivery mental model
Turn every source change into traceable evidence.
The course uses GitHub Actions as a concrete pipeline-as-code implementation while keeping the concepts portable to Jenkins, GitLab CI, Azure Pipelines and other delivery systems.
Promote known-good bits
Artifact ↓ Staging verify ↓ Production + rollback
Build once, preserve artifact identity and promote deliberately.
Pipeline in one minute
Source → build → test → package → verify → promote → observe.
INTEGRATEsource · build · tests
PACKAGEEVIDENCEartifact · checksum · provenance
PROMOTEDELIVERenvironment · health · rollback
The included lab validator runs credential-free on a Linux host. It executes the local build, test, artifact, promotion and rollback mechanics and statically verifies representative GitHub Actions workflow structure. Publishing the workflow to a learner-owned GitHub repository is an optional online exercise.
Course modules
Build reliable feedback before automating production.
Every module includes objectives, implementation detail, copy-pasteable examples, a guided lab, expected results, troubleshooting guidance, real-world context and a knowledge check.
01
CI/CD foundations and feedback loops
Understand continuous integration, continuous delivery and continuous deployment as engineering feedback systems rather than a collection of automation tools.
Open module →02Pipeline as code with GitHub Actions
Define workflows in version-controlled YAML and understand events, workflows, jobs and steps.
Open module →03Events, jobs, steps and runners
Control execution order, isolate work into jobs and understand the trust boundary created by hosted and self-hosted runners.
Open module →04Reproducible builds, dependencies and cache
Make builds deterministic first, then use dependency caches to improve speed without confusing cache data with release artifacts.
Open module →05Tests, quality gates and build matrices
Layer fast checks, tests and compatibility matrices so a pipeline reports useful evidence instead of a single opaque pass/fail result.
Open module →06Artifacts, outputs and release evidence
Move data deliberately between jobs, preserve build outputs and separate tiny job outputs from file artifacts.
Open module →07Secrets, token permissions and OIDC
Reduce credential exposure with least privilege, protected secrets and short-lived identity federation.
Open module →08Environments, approvals and concurrency
Protect deployments with environment-specific controls, deliberate promotion and concurrency rules that prevent overlapping releases.
Open module →09Container builds, registries and provenance
Treat container images as immutable delivery artifacts, use meaningful tags/digests and understand the role of provenance.
Open module →10Deployment strategies, health and rollback
Use verifiable deployment steps, health checks and a tested rollback path instead of treating a successful command exit as proof of service health.
Open module →11Reusable workflows, governance and troubleshooting
Reduce pipeline duplication, pin external dependencies deliberately and troubleshoot from run context before rerunning blindly.
Open module →12Capstone: build, test, package, promote and rollback
Combine source identity, quality gates, immutable artifacts, staging verification, controlled promotion and rollback into one auditable delivery flow.
Open module →Prerequisites
Git knowledge is required; container and Kubernetes knowledge improves the later modules.
The core validator does not require GitHub credentials or a cloud account.
Git & GitHub Fundamentals
Required. Learners should understand commits, branches, remotes and pull-request collaboration.
Linux / shell
Required for local labs. Bash, file operations and exit codes are used throughout.
Docker / Kubernetes
Recommended. Container artifact and deployment examples connect naturally to the existing Docker and Kubernetes Fundamentals courses.
Knowledge assessment
Prove you understand delivery controls, not just workflow YAML.
The assessment selects 30 questions from an 84-question bank covering CI/CD foundations, workflow execution, reproducible builds and caching, quality gates, artifacts and releases, security and identity, environments, deployment strategies and troubleshooting. Pass mark: 75%. Time limit: 35 minutes.
12 MODULES→30 RANDOM QUESTIONS · 35 MIN→PASS ≥ 75%→OPTIONAL CERTIFICATION
Maximum two attempts per 24 hours. Learning and assessment are free. A passing result enables the optional ₹499 GST-inclusive Certificate of Successful Completion pathway.
Course capstone
Build, test, package, verify, promote and rollback one immutable release.
Module 12 creates a source identity, required quality gate, checksummed artifact, staging health verification, production release record and deterministic rollback path. The same control flow maps directly to a production GitHub Actions pipeline.
Build→Test→Artifact→Staging→Promote→Rollback