In Part 1 — Jenkins Fundamentals: What Are We Actually Operating?, we built the mental model for Jenkins: the Controller receives a build request, the Queue holds work waiting for execution capacity, an Executor provides a slot to run the workload, and a Workspace becomes the build's working directory.
Now we are going to make that model concrete.
In Part 2, we will launch a single Amazon EC2 instance, install a Jenkins Controller manually, complete the initial setup, and run our first Pipeline directly on the Controller. This is intentionally the simplest architecture in the series: easy to understand, easy to inspect, and deliberately not our production target.
By the end of the lab, the concepts introduced in Part 1 should no longer feel abstract. You will be able to identify the Jenkins process, JENKINS_HOME , the built-in node, its Executor, a real Workspace, Console Output, and an archived Artifact.
1.…