Command Palette

Search for a command to run...

Hectal
Phase 4Intermediate5 of 9 in CI/CD

GitLab CI/CD

One YAML file, deeply integrated with GitLab itself — the third major platform's own take on the exact same pipeline model.

GitHub Actions is fully hosted; Jenkins is fully self-managed. GitLab CI/CD sits in between — it can be self-hosted or use GitLab's own hosted runners, and its single .gitlab-ci.yml file is arguably the most compact expression of Phase 0.2's universal pipeline model of any platform in this course.

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

.gitlab-ci.yml: Stages and Jobs

GitLab CI/CD is configured through exactly one file, .gitlab-ci.yml, at the repository root — stages define order, jobs define the actual work, and jobs in the same stage run in parallel by default, same as everywhere else.

13 min 1 code practice

2
4.2

GitLab Runners & Executors

A GitLab Runner is the agent that actually runs jobs — and its EXECUTOR determines exactly how: a Docker container, a shell on the host machine, or several other genuinely different isolation models.

13 min 1 diagram 1 code practice

3
4.3

Environments & Deployment Jobs

GitLab's environment: keyword tracks exactly what's deployed where, and manual jobs give a human-triggered deployment gate — the same production-safety concept from Phase 2.2, expressed through GitLab's own mechanism.

13 min 1 diagram 1 code practice

4
4.4

Rules, Includes, and Templates

rules: gives fine-grained control over exactly when a job runs, and include: splits a growing pipeline across multiple files — GitLab's own answers to Phase 1.1's triggers and Phase 2.3's reusable workflows.

14 min 1 code practice