Most outages begin with a change. Continuous integration and continuous delivery (CI/CD) reduce that risk by building, testing, and packaging every change automatically, so problems show up in minutes instead of after a release. Release engineering is the discipline of getting those changes into production safely and repeatably.
You'll start with what a CI/CD pipeline is and how its stages fit together, then build a working one with GitHub Actions. Next you'll compare deployment strategies such as rolling, blue-green, and canary releases, which limit the damage when a change goes wrong, and finish with how security checks fit into the same pipeline.
With a safe path to production in place, you'll be ready for the next module, Monitoring & Observability, which shows how to see what your systems are doing once a release is live.
The basics of continuous integration and delivery, and how automating build, test, and deploy steps improves productivity and code quality.
How GitHub Actions automates developer workflows, with a hands-on pipeline that builds a project into a Docker image and pushes it to a registry.
A comparison of three common ways to release a new version, and the trade-offs each makes between speed, cost, and the risk of a bad release.
An overview of building security checks into the delivery pipeline, so vulnerabilities are caught before a change reaches production.