The Overview of Jenkins
HI Hi, Greetings! 
Intimate February 
Today, I would like to share with you an article about the overview of Jenkins. I hope this article has more support DevOps Let's move to the article and I will explain the last part of this article.
PART 05:
Jenkins' Architecture - II
Master- Agent (Slave) Architecture In Jenkins
Jenkins uses a master-agent (or distributed) architecture to manage distributed builds. The TCP/IP protocol is used to communicate between the Master and the Agent(s).
The Jenkins Master and Agent(s) have the following roles and responsibilities:
Jenkins Master
The Master is Jenkins' main server. Jenkins Master is in charge of the following tasks:
Arrange for construction projects to be completed.
Determining which agent in the master-agent ecosystem should be used to dispatch the builds.
Keep an eye on agents and bring them online/offline as needed.
Presenting the developer with the build results (and reports).
The Jenkins master can also run the jobs directly, however for build and execution-related tasks, it's best to use the appropriate agent(s).
Jenkins Agent (Slave)
A remote machine connecting to the Master is known as an agent. 'N' number of agents could be chosen depending on the project and build needs. Agents can run on a variety of operating systems, and the Master selects the appropriate Agent for build execution and testing based on the 'kind of build request.'
The Jenkins Agent(s) are in charge of the following tasks:
Pay attention to the Jenkins Master's commands.
Carry out build jobs that the Master has dispatched.
Developers have the option of running the build and execution tests on a specific agent or kind of agent. Jenkins Master selects the best-suited Agent for the job as the default option.
In a Master-Agent Architecture, How Does Jenkins Work?
The brief roles of the Master and Agent(s) in Jenkins were discussed in the preceding section of the What is Jenkins blog. Let's take a closer look at how Jenkins functions in a Master-Agent (or distributed) architecture:
There are three Agents in the Jenkins Master-Agent architecture shown below, each running on a separate operating system (i.e. Windows 10, Linux, and Mac OS).
Developers check-in their modifications to 'The Remote Source Code Repository,' which is shown on the left-hand side.
The Jenkins master is the only one connected to the repository, and it checks for code changes at regular intervals. The Jenkins Master is connected to all of the Jenkins Agents.
Jenkins master sends the build and test requests to the appropriate Jenkins Agent, based on the environment needed to complete the build. This allows you to run builds and tests in a variety of contexts across the architecture.
The Agent runs the tests, generates test results, and transmits them to the Jenkins Master for review.
Jenkins Agents can execute multiple builds versions of the code for different platforms as developers continue to push work. Jenkins Master (or Master Node) is in charge of how the various builds should run.
We'll look at the processes for setting up Jenkins Master and Agents in later sections of the What is Jenkins blog.
You are welcome to like and leave feedback in the comment area.
Link:
PART 01:
The Overview of Jenkins - PART - 01
PART 02:
The Overview of Jenkins - PART - 02
PART 03:
The Overview of Jenkins - PART - 03
PART 04:
The Overview of Jenkins - PART - 04
Source:
www.jenkins.io/doc/
www.lambdatest.com/blog/what-is-jenkins/
www.lambdatest.com/blog/what-is-jenkins/
M M Zaheer Hussain
Stay Safe!
