Jenkins CI/CD Course
Write a Jenkinsfile you would actually ship - triggers, credentials, matrix builds, a Java pipeline and a rollback that works.
Take this course in the learning hubLessons
- CI, delivery and deployment are three thingsThe three terms people use interchangeably promise different things and cost different amounts.
- Controller, agents and executorsJenkins schedules on one controller and builds on agents, and executors are the slots that decide throughput.
- Why Pipeline replaced freestyle jobsMoving the build definition into the repository is what made Jenkins jobs reviewable, branchable and disposable.
- Anatomy of a declarative JenkinsfileOne pipeline block, a mandatory agent, stages of steps, and a post block that runs whatever happened.
- Triggers: polling, webhooks and cronHow a build starts decides how much load Jenkins puts on your SCM and how fast feedback arrives.
- Environment variables and parametersJenkins injects a fixed set of variables, and parameters are how a human or another job varies a run.
- Credentials without hardcoding secretsA Jenkinsfile should name a credential id and never contain the secret behind it.
- Artifacts, fingerprints and test resultsWhat the build produced and what the tests said are published deliberately, and they decide the build result.
- Parallel stages and matrix buildsParallel splits one build across executors, and matrix multiplies it into a cell per axis combination.
- Agents from Docker imagesRunning a stage inside a container makes the toolchain part of the repo instead of part of the machine.
- A real Java pipeline, end to endBuild, test, gate on quality, publish an image and deploy - assembled one directive at a time.
- Blue-green deploys and rollbackTwo production stacks and a router turn rollback into a switch flip instead of a rebuild.
- Shared libraries for pipelines you stop repeatingOne git repo of Groovy turns forty near-identical Jenkinsfiles into forty calls to one reviewed step.
- When the pipeline breaksThe common Jenkins failures have specific causes, and Replay plus the linter find most of them in minutes.
- Slow, flaky and dangerous pipelinesThe controller is a single point of failure, and most pipelines treat it as a build machine.