Releasing software by hand is slow and risky: someone has to build the code, run the tests, package it and copy it to the right servers, and every manual step is a chance for a mistake. CI/CD automates all of it. Continuous integration (CI) builds and tests your code automatically every time it changes, and continuous delivery or deployment (CD) then releases the tested result to your environments.
You'll start with the core ideas behind pipelines, then build them with three of the most widely used tools: GitHub Actions, Jenkins and GitLab CI/CD. Each one defines a pipeline as code that runs your tests, builds container images and deploys them. You'll finish with GitOps and Argo CD, where Git is the single source of truth for what runs in your Kubernetes cluster. Watch the videos in order, then move on to Monitoring & Observability.
A short introduction to continuous integration and continuous delivery and why teams automate their releases.
The basic concepts of GitHub Actions, then a pipeline that builds and pushes a Docker image.
How to create, configure and manage Jenkins pipelines, from basic concepts to multi-stage builds.
Build a complete GitLab pipeline that runs tests, builds a Docker image and deploys it to a server.
How Argo CD keeps a Kubernetes cluster in sync with Git, with a hands-on demo of an automated delivery pipeline.