Launching an APP: Automation through Jenkins

Image Source: Medium

Launching an app is not a tedious task in setting up a server. The main task is what proceeds it. The testing of the app, making the data persistent, keeping up with the launched app so that it doesn’t stop working and the most important one, informing the developer to relaunch the pod if incase it has shut down could be both tiring and a time-consuming process. The workload could be shared by other technologies such as Kubernetes, Github, Git and not to forget the one that integrates them all JENKINS.

In the following demo, I have given a complete description of how to create a build pipeline of a series of jobs each performing a specific task and integrating to complete the whole demo.

Heading forward to job 1

🎃 Pull the Github repo automatically when some developers push the repo to Github.

The question is how will the admin know that some changes have been made to the code. This can be possible in two ways:

1. If the admin keeps an eye on the Github repo and as soon as any change is made, pull the repo or to do this work automatically, Github could be integrated with Jenkins and through Poll SCM, if any changes are made, the Github repo could be pulled automatically.
2. The admin could have direct contact with the developer. The developer…