DevOps Bootcamp

Master agent architecture in Jenkins

Let’s consider a scenario where we have specific tools, which are on a different server and these tools are part of an important phase of application life cycle management.

In that case, we can use our Jenkins server as a master and the server with specific tools as the agent. In this way, master Jenkins can access resources available on other servers to execute specific operations.

Go to Manage Jenkins and click on Manage Nodes. We can see the master node available on which our Jenkins is installed. To add a new node that might have a different operating system and tool set, we need to click on New Node:

Give a node name and select it as a Permanent Agent. Click on OK. Enter Name, Labels, and Remote ...