Jenkins and it s Architecture.

DevOps Series 2.

Jenkins is a automation tool, written in java with plugins built for continuous Integration purpose. Plugins allow integration of various DevOps Stages.

Suppose you need to automate the process which means the development team gives the code to the time to code is deployed onto the production servers.

In order to automate entire software development life cycles , jenkins provides various interfaces and tools in order to automate the entire process.

Suppose you have a git repository, where the development team commits to code and then Jenkins takes over from there. Jenkins pull that code and then it will move it to that commit phase where the code is committed to every branch.

Then Jenkins moves it and then it goes to the build phase ,where it will compile the code now. After the code is compiled and validated and reviewed, the code is tested.

Once all the tests are done and it is finally packaged into application, it could be either a war file or jar file

What Jenkins does is pull your code from version control system, then it is going to perform the build. It is going to compile your code. It is going to validate your code. It is going to again review the complete code, after that it will perform the unit testing and integration testing and finally it will package your application into war file or jar file and then it is ready to delivered.

Jenkins role is only until the application is packaged and it is delivered.

Master /slave architecture of Jenkins.

Jenkins master distribute it workload to slaves. Jenkins slaves are required to provide desired environment .It works on the basis of requests received from Jenkins Master.

As shown in the below diagram, Jenkins use slaves for testing in different environment and so on. In this Jenkins check the git repository at periodic intervals of time.