Every push tested, every merge shipped. GitHub Actions first, then Jenkins and GitOps.
Everything this course covers, in the order you'll learn it. Open a stage to see why it matters and jump to its lesson.
Know what a pipeline is for before writing one.
Lesson 1: What a pipeline is for →The quickest way to get a real pipeline running on your own repo.
Lesson 2: GitHub Actions: your first real pipeline →Make pipelines fast and readable instead of slow and copy-pasted.
Lesson 3: Workflow details: expressions, matrices, caches and artifacts →Deploy without pasting passwords into YAML.
Lesson 4: Secrets, environments and OIDC: deploy without leaking keys →The pipeline is only as useful as the checks it runs.
Lesson 5: Testing in pipelines: lint, unit, integration and the gate →Turn code into a versioned artifact that can be deployed anywhere.
Lesson 6: Build and publish: images you can trust and find again →Get that artifact onto servers, and back off them when something breaks.
Lesson 7: Deploy: static sites, servers over SSH, Kubernetes, and rollbacks →Still everywhere in big companies. You will meet it at work.
Lesson 8: Jenkins: the controller, agents, Jenkinsfile and shared libraries →Same ideas, different YAML. Read any pipeline you are handed.
Lesson 9: Other CI tools: GitLab CI, CircleCI and Buildkite →Let Git be the source of truth for what runs in the cluster.
Lesson 10: GitOps: Git says what runs, the cluster makes it so →Pipelines hold the keys to production. Treat them that way.
Lesson 11: Pipeline security: your CI is a production system →Keep CI fast and cheap as the team and the repo grow.
Lesson 12: Scaling pipelines: reuse, your own runners, speed and cost →Stage order follows the community roadmap at roadmap.sh/devops, trimmed to what DevOps work needs.