Menu

1 / 16

Jenkins Fundamentals - Part 3: Adding Static Jenkins Agents on AWS EC2

DEV Community: jenkins·Phu Hoang·about 6 hours ago
#c2HYrREp
#devtojenkins#devto#dev#agent#jenkins
Long article (4025 words) — no AI summary yet.
Reading 0:00
15s threshold

In Part 2 — Installing Jenkins Controller on AWS EC2 , we installed Jenkins on a single EC2 instance and intentionally allowed the built-in node to execute our first Pipeline. That gave us the simplest possible Jenkins environment, but it also exposed the main weakness of the all-in-one model: orchestration and build execution share the same machine .

Part 3 separates those responsibilities.

The existing EC2 instance remains the Jenkins Controller, while a second EC2 instance becomes a static Jenkins Agent. The Controller keeps responsibility for the Queue, scheduling, Pipeline orchestration, configuration, and Jenkins state. The Agent provides the Executor, Workspace, build tools, and compute resources used by the Pipeline.

By the end of Part 3, our architecture will move from Controller + build workload on one EC2 instance to a traditional distributed Jenkins model with a dedicated Controller and a dedicated build worker.

1.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.