Agents and Docker
Part of the Jenkins course
The build passed on Tuesday and failed on Wednesday, with no change to the code. It turns out Tuesday's build landed on the agent where somebody had installed Node 20, and Wednesday's landed on the one still running Node 16. That is "works on my machine", except now the machine is a build server and nobody can tell you which one ran your job.
Every step in a pipeline runs somewhere, and so far agent any has been letting Jenkins decide where. This lesson is about deciding on purpose: pinning by label when the hardware matters, and running inside a container when the tooling matters. ...
Want to learn Jenkins Agents and Docker in a real environment?
Click below, get a fresh Linux box with Jenkins ready to go, and work through Agents and Docker hands-on with an AI tutor that knows your code.
Start this lessonAgents and DockerWhat you'll learn
- Agent any vs agent none
- Agent labels
- Agent docker
- Agent kubernetes
- Per-stage agents
Read this lesson in your language
All lessons in this course
11 lessons- 1What Is Jenkins20 min
- 2Your First Freestyle Job25 min
- 3Your First Declarative Pipeline30 min
- 4Stages, Steps, and Post Blocks30 min
- 5Artifacts and Test Results25 min
- 6Environment and Credentials30 min
- 7Parallel and Matrix Builds30 min
- 8Agents and Docker30 min
- 9Triggers and Schedules25 min
- 10Shared Libraries30 min
- 11Capstone: Pipeline as Code for a Node.js App45 min
Explore other courses
