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 04:
Jenkins' Architecture - I
We must first grasp Jenkins' architecture before diving into how it works. The interplay between distinct aspects in Jenkins is outlined in this series of steps:
Developers make the required changes to the source code and commit them to the repository. In the version control system that is used to maintain the source code repository, a new version of that file will be created.
The Jenkins CI server monitors the repository for changes (in the form of code or libraries), and any modifications are pushed to the server.
The next step is to check whether the build with the 'pulled changes' is proceeding or not. If the build process is successful, the Build server runs a build with the code and generates an executable. If a build fails, an automated email is delivered to the developer with a link to the build logs and other build artifacts.
The built application (or executable) is deployed to the test server if the build is successful. This stage aids in the implementation of continuous testing, in which the freshly created executable is subjected to a series of automated tests. If any functionality has been broken as a result of the changes, developers will be notified.
If the checked-in code does not have any build, integration, or testing issues, the modifications, and tested application are automatically deployed to the Prod/Production server.
It's possible that a single Jenkins server won't be enough to meet the following requirements:
Testing must be done in a variety of contexts (i.e., code created in various languages such as Java, Python, C, and others is committed to a version control system), and a single server may not be sufficient.
A single Jenkins server may not be able to handle the demand that large-scale software projects entail.
Jenkins' distributed (or Master-Agent) architecture is utilized for continuous integration and testing in such settings. We look at Jenkins' architecture to get a better understanding of how it operates.
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 05:
Source:
www.jenkins.io/doc/
www.lambdatest.com/blog/what-is-jenkins/
M M Zaheer Hussain
Stay Safe!
