Introduction
In our ongoing #90DaysOfDevOpsChallenge, Day 28 takes us into the realm of Jenkins Agents, a crucial aspect of scaling CI/CD infrastructure. As we delve into this topic, we'll unravel the intricate dynamics between Jenkins master servers and agents, understanding their roles in orchestrating and executing workflows efficiently.
Understanding the Jenkins Ecosystem
Jenkins master servers serve as the nerve center, overseeing configurations, job scheduling, and workflow monitoring. However, for scalability and optimized execution, the introduction of Jenkins agents becomes imperative. Agents, whether in the form of dedicated machines or containers, function as the hands-on executors, carrying out the granular steps defined within a job.
The Significance of Jenkins Agents
Scalability and Distribution
In the context of growing project complexities and team sizes, a monolithic Jenkins setup might become a bottleneck. Enter Jenkins agents. These distributed entities enable a scalable approach, ensuring efficient handling of job execution.
Master-to-Agent Connection
The master-to-agent connection mechanism allows for a decentralized architecture. Instead of burdening a single system with UI rendering and job execution, Jenkins master servers can delegate execution tasks to connected agents. This separation optimizes resource utilization and enhances overall system performance.
Preparing for Jenkins Agents
Before we dive into the practical tasks, it's crucial to set the stage. A fresh Ubuntu 22.04 Linux installation should have Java (matching the version on the Jenkins master server) and Docker installed. Additionally, meticulous attention to user rights, permissions, and ownership for Jenkins users is paramount.
Task-01: Setting Up a Jenkins Agent
Create an AWS EC2 Instance: Initiate an AWS EC2 instance and establish a secure connection with the Jenkins master, ensuring the necessary SSH setup and key pair exchange.
Verify Agent Status: Confirmation of a successful agent setup can be found under the "Nodes" section in Jenkins. This visual validation ensures a seamless connection between the master and the agent.
Task-02: Running Jobs on the New Agent
With the agent in place, it's time to put it to work. Execute the jobs crafted on Day 26 and Day 27 specifically on this newly configured agent. Leverage labels to instruct the master server to trigger builds on the designated agent server.
Conclusion
Day 28 serves as a gateway to a distributed Jenkins architecture. By comprehending the master-to-agent connection and witnessing its implementation in a practical scenario, we equip ourselves with the tools to scale and optimize our CI/CD infrastructure effectively.
Stay tuned for more profound insights and hands-on experiences that elevate your mastery in DevOps practices.
Pipeline created.
Build History.
dev-server agent created.
Console Output.
Node todo cicd pipeline created.
App deployed on EC2 instance.