Command Palette

Search for a command to run...

Hectal
Phase 3Intermediate4 of 9 in CI/CD

Jenkins

The same pipeline model from Phase 0.2, now expressed as a controller dispatching work to agents, written in a Jenkinsfile committed to your own repository.

GitHub Actions is fully hosted and managed by GitHub itself. Jenkins is the opposite: open-source, self-hosted, and running on infrastructure you own — genuinely still one of the most widely deployed CI/CD tools in real enterprises, especially where GitHub isn't the source control platform at all, or where genuinely deep customization is needed.

0/4 · 0%
4 topics ~54 min 7 code blocks & diagrams
Start with the first topic
1
3.1

Jenkins Architecture: Controller & Agents

A Jenkins CONTROLLER is the brain coordinating everything; AGENTS are the actual machines that run jobs — directly mirroring Kubernetes' own control-plane-versus-worker-node split, just for a CI system instead of a container orchestrator.

13 min 1 diagram 1 code practice

2
3.2

The Jenkinsfile & Declarative Pipelines

A Jenkinsfile, committed directly into your repository, defines the entire pipeline as code — the same 'pipeline config lives in the repo, reviewed like any other change' principle every platform in this course shares.

14 min 1 code practice

3
3.3

Credentials & Plugins

Jenkins' Credentials store keeps secrets out of a Jenkinsfile exactly the way GitHub Actions Secrets do — and its enormous plugin ecosystem is both Jenkins' biggest strength and its most common source of real operational headaches.

14 min 2 code practice

4
3.4

Multibranch Pipelines & Shared Libraries

A Multibranch Pipeline automatically discovers and builds every branch (and pull request) in a repository — and a Shared Library extends the reusable-workflow idea from Phase 2.3 to Jenkins' own Groovy-based pipelines.

13 min 1 diagram 1 code practice