Command Palette

Search for a command to run...

Hectal
Phase 0Beginner1 of 9 in CI/CD

The CI/CD Mindset

Why manual releases fall apart, the pipeline model every CI platform shares, and the build systems that actually turn source code into something deployable.

Git gets your code into a shared repository. Docker packages it into a runnable image. Kubernetes runs it in production. CI/CD is the automation connecting all three — the thing that actually builds, tests, and ships a change the moment it's merged, without a human running commands by hand each time.

The same loop as every other course here: Learn → Close the tutorial → Explain without notes → Try it in a real terminal → Break it → Fix it → Explain the trade-off.

0/4 · 0%
4 topics ~53 min 6 code blocks & diagrams
Start with the first topic
1
0.1

Why CI/CD Exists

Continuous Integration catches problems the moment code is merged, by building and testing automatically — Continuous Delivery/Deployment extends that same automation all the way to actually shipping the result.

13 min 1 diagram practice

2
0.2

The Pipeline Model: Stages, Jobs, and Runners

Every CI/CD platform — Jenkins, GitHub Actions, GitLab CI — shares the same underlying vocabulary: a pipeline of stages, each containing jobs, each executed by a runner or agent somewhere.

13 min 1 diagram practice

3
0.3

Build Systems Primer: Maven vs Gradle

Every CI pipeline for a Java project runs a build tool underneath it — Maven and Gradle both turn source code into a deployable artifact, following the same lifecycle idea with genuinely different philosophies.

14 min 1 diagram 1 code practice

4
0.4

Your First Pipeline

A minimal, real pipeline — checkout, build, test — running on every push, is the entire foundation everything in this course builds on top of.

13 min 2 code practice