Now the first question is, What is Continuous Integration?
Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times. Basically, CI is a process in which all development work is integrated and the resulting work is automatically tested and built. The idea behind CI is that development errors are identified very early in the process.
Suppose there is multiple developers are working on the same Project and they are using the same repository to check-in the code.
Anyone can check-in the error code on the server. Now all users, Who are using this server will face the same error. We can resolve this using Continuous Integration. There are many tools of Continuous Integration, Jenkin is one of them.
Jenkins is the tool or mechanism which inform all users about the corrupt build if anyone check-in the error code.
What is the Jenkins integration server?
Jenkins is open source tool to perform the continuous integration. The basic functionality of Jenkins is to execute a predefined list of steps based on a certain trigger.
The list of steps can for example include:
perform a software build with Apache Maven or Gradle
Run a shell script
Archive the build result
Afterward, start the integration tests
Jenkins also monitors the execution of the steps and allows to stop the process if one of the steps fails. Jenkins allows notifying users about the build success or failure.
You can extend the Jenkins to create the Building or test the project Build or application. Jenkins also supports the GIT, We will look into this in coming tutorial.