How has Jenkins evolved in the market?
Jenkins is an open-source automation server through which we can automate our whole environment.
Now I’m about to present you two different scenarios first without using Jenkins and second using Jenkins. This presentation will make you understand the complete scenario.
First Scenario:
Our company provides cab services, One day the product manager of our
the company finds a beneficial offer after doing some market research and schedules a meeting with the core team of the company.
When the meeting is done and the offer is finalized then the developer starts working on it. Our company uses an SCM i.e. GitHub.
The repo in GitHub has four branches (master branch, Team A: front-end developer, Team B: back-end developer, and integration team). In team A the front-end code is updated. In Team B back-end code is updated. The integration team integrates the code and pushes the code into the C branch.
Here the role of the testing team comes in. The testing team downloads the code from C then complies with it and then tests it, if there is some compilation error in the code the team sends feedback to both the front-end and the back-end developer immediately. If no error is found the turn-off operation team comes to create a testing environment and they deploy this app and start testing if again there is an error feedback will be sent. If there is no error we approve this app and push it into the master branch.
Now, this code is updated in the production world. Now the client can easily use these offers.
Second Use Case :
There is another company which is our competitor, they have already before we deployed the same offer in the production world. Their customer rate has already been increased in our comparison, we suffer a loss.
We both did the same thing but they did before us. How is it possible?? Let’s discuss this in-depth !!!!
The other company did the same as we did before. They studied the market and discussed the same with the core team members. The developer started implementation.
But after this task, the company automated the whole process. Let’s see how….????
In the testing task, we manually create a testing environment, if some fault we send an email to the developer. But the other company created automation and make the testing environment completely automated.
They used a trigger in Jenkins. The use of Jenkins will do the same integration process in an automated way as our company did. As our integration team updates, all the code in their branch As the update is done in-branch GitHub sends a notification to Jenkins As soon as it receives the notification then downloads the code then it creates a testing environment and tests the code if some error is there it sends an email to the developer, if no error then it updates the master branch there is also a trigger of Jenkins in the master branch as soon as the master branch updates it receives notification from GitHub Here Jenkins publishes the master branch’s code in production server.
Hope You Enjoy this Blog !!