DEV104 · Continuous Integration and Delivery (CI/CD)
About Course
Build pipelines that automatically test, package and deploy every change. You will create a GitHub Actions workflow with quality gates, caching, secrets and staged deployment for a small web application.
Who it is for
Developers and operations staff who use Git and want every change to be built, tested and released automatically and safely.
Prerequisites
Complete DEV103 or be comfortable with Git branches, pull requests and GitHub.
What you will be able to do
- Describe the stages, triggers, jobs and artifacts of a CI/CD pipeline.
- Write a GitHub Actions workflow that lints, tests and builds an application with caching and a test matrix.
- Manage secrets, permissions and environments securely in a pipeline.
- Choose and configure a deployment strategy with approvals and a rollback path.
Lessons
- Lesson 1 · Anatomy of a CI/CD pipeline
- Lesson 2 · Fast, reliable and secure CI
- Lesson 3 · Continuous delivery and deployment strategies
- Lesson 4 · Lab and assignment
Lab: Build a CI/CD pipeline with GitHub Actions
Starting from a small Vite web app with unit tests, you will write a workflow that runs on pull requests and pushes, lints and tests on two Node.js versions, caches dependencies and uploads the build as an artifact. You will then add a deployment job to GitHub Pages that runs only on main, through a protected environment, and practice a rollback.
Free tools: GitHub free with GitHub Actions and GitHub Pages, Node.js LTS, VS Code, and the free act tool to run workflows locally (optional)
Assessed assignment
Create a complete pipeline for a small business web app of your choice, such as a bakery's ordering page or a clinic's information site. The pipeline must run on every pull request and push, include lint, unit test and build stages, use dependency caching, publish test results or a build artifact, keep any secret in GitHub secrets, and deploy automatically from main to a protected environment. Document in a README the pipeline diagram, the average run time before and after caching, and the exact steps to roll back a bad release.
| Criterion | Weight | What excellent work looks like |
|---|---|---|
| Pipeline design | 30% | Stages are ordered logically, triggers are correct, and failures stop the pipeline before deployment. |
| Efficiency | 20% | Caching and parallel jobs reduce run time, and the measured improvement is documented. |
| Security | 25% | Secrets are never printed or committed, workflow permissions are minimal and third-party actions are pinned. |
| Deployment and rollback | 25% | Deployment runs only from main through an environment, and the rollback procedure works as documented. |
Portfolio piece
A documented GitHub Actions pipeline that tests, builds and deploys a web app automatically with a tested rollback procedure.
Next step
Continue with DEV105 · Containers with Docker · 8 hours · $56.00
Course Content
DEV104 · Continuous Integration and Delivery (CI/CD) (6 h)
-
Lesson 1 · Anatomy of a CI/CD pipeline
-
Lesson 2 · Fast, reliable and secure CI
-
Lesson 3 · Continuous delivery and deployment strategies
-
Lesson 4 · Lab and assignment
-
DEV104 Assessment · Continuous Integration and Delivery (CI/CD)