In my old days working as developer we used to run the build manually by sharing the war files to the system engineer to deploy the war file on the server. Each developer has to follow the same process by running the build in local and share the war file with the engineer. We need to run the build manually every time when there is a fix or code change in the module and instructions was given to share the latest war file before leaving for the day. In those days the code was committed in the VSS but does not have the process to trigger the build for all the components.

Now the process is very much simpler, well defined & organized by implementing the standard DevOps practice across projects & departments. The above mentioned problem is solved by implementing the Continuous Integration practice in the organization.

Continuous Integration is a development practice that requires developers to integrate code into a shared repository at regular intervals.

Continuous integration requires the developers to have frequent builds. The common practice is that whenever a code commit occurs, a build should be triggered by implementing the Jenkins Tools which is based on open source.

Jenkins is software that fulfils continuous integration. Jenkins will be installed on a common server to initiate the build for multiple modules. Let’s see below the Jenkins Flowchart:-

 

 

 

Now let’s go through the below section for you to play around with Jenkins:-

  

1)       Jenkins Installations: - You can download the Jenkins from https://jenkins.io/index.html link and i have downloaded in             D: of my machine.

    1.   Open the command prompt as Administrator and execute the below command:-

D:\>Ja Running from: D:\jenkins.war

Webroot: $user.home/ .jenkins

April 02, 2016 4:10:46 PM winstone.Logger logInternal

INFO: Beginning extraction from war file

Once the processing is complete without major errors, the following line will come in the output of the command prompt.

INFO: Jenkins is fully up and runningva –jar Jenkins.war

            Access the Jenkins by typing the localhost:8080 in browser

 

2)      Jenkins Tomcat Setup: - The tomcat server can be downloaded from https://tomcat.apache.org/download-70.cgi site.

    1. Assuming the Java setup is done before tomcat installation.
    2. Unzip the tomcat file and copy the Jenkins war file in the webapps folder of tomcat.
    3. Go to Tomcat bin folder and execute the startup.bat file to start the tomcat server.

 

Once the Tomcat is up & running without any major errors then type the localhost/Jenkins in the browser and you will see the Welcome Message from Jenkins.

 

3)      You can setup the Jenkins with your preferred repository either GIT, Maven etc.  Please send an email to me at riteshkumarb@yahoo.com if you need Jenkins setup details with GIT or Maven.

 

4)      You need to implement & configure the Jenkins for  below features:- 

    1. Setup Build Jobs
    2. Notification
    3. Automated Testing
    4. Automated Deployment
    5. Reports