JenkinsTutorial step by step

Jenkins – The Final Notes

  1. Introduction

  • Jenkins is an open source continuous integration tool written in Java.
  • Jenkins provides continuous integration services for software development. I
  • It is a server-based system running in a servlet container such as Apache Tomcat.
  • Jenkins, a continuous build tool, automating the build, artifact management, and deployment processes

CI – The tools

Code Repositories
SVN, Mercurial, Git

Continuous Build Systems
Jenkins, Bamboo, Cruise Control

Test Frameworks
JUnit,Cucumber, CppUnit

Artifact Repositories
Nexus, Artifactory, Archiva
  1. How Jenkins Work

  1. Setup Level:

Here we can choose what Options, Tools and plugins we can use with Jenkins
  • Associating with a version control server
  • Triggering builds :Polling, Periodic, Building based on other projects
  • Execution of shell scripts, bash scripts, Ant targets, and Maven targets
  • Artifact archival
  • Publish JUnit test results and Javadocs
  • Email notifications
  1. Building

Once a project is successfully created in Jenkins, all future builds are automatic Building
  • Jenkins executes the build in an executer
  • By default, Jenkins gives one executer per core on the build server
  • Jenkins also has the concept of slave build servers
  • Useful for building on different architectures
  • Distribution of load
  1. Reporting

  • Keeping track of build status: Last success and failure
  • Unit test coverage Test result trending Findbugs, Checkstyle, PMD
  1. Types of Environments

  1. Development
  2. QA  only Functional testing of the system
  3. Integration Testing Tests the system from end to end
  4. User Acceptance Testing(UAT) user will validate the functionality over time
  5. Production == Production
  6. Production Parallel A parallel of production to replicate production issues
  7. CERT CERT is Certification environment! It’s just where you certify your product so that it can move to production

  1. Installing Jenkins

  • You can check the current version of Java that is installed on your machine by typing following command in command prompt.
    Java Version

  • Jenkins is distributed in the form of a bundled Java web application (a WAR file). You can download the latest version from the Jenkins website

  • Downloaded the WAR file, simply deploy the Jenkins.war file to your application server—with Tomcat. Extract and Place jenkins.war file in Tomcat’s webapps directory. Or Deploy using http://localhost:8080/manager Tomcat UI

  1. Configure Jenkins

  1. Configuring Java

Manage Jenkins → Configure System → JDK Installations → Add JDK

  1. Configuring ANT & MAVEN

Manage Jenkins → Configure System → ANT & MAVEN
  1. Secure Jenkins

Manage Jenkins → Configure Secure Jenkins
[Tick] Enable Security
[Select]   Jenkins own user database
[Tick] Allow users to Signup
[Select]   Matrix based Security
[add] User Group and give all the access
  1. Plug-in management

Manage Jenkins → Manager Plugins 
link and search for the plugin you want to install. Select it from the list and select to install it and restart Jenkins.
You can manually restart Jenkins by adding restart as URL parameter.
  1. Setting up a Jenkins job

The build of a project is handled via jobs in Jenkins. Select New Item from the menu
  1. Ant Project Configuration in Jenkins

a. Ant basics

ANT stands for Another Neat Tool. It is a Java-based build tool from Apache. 
It will do
  • Compiling the code
  • Packaging the binaries
  • Deploying the binaries to the test server
  • Testing the changes
  • Copying the code from one location to another

Typically, Ant's build file, called build.xml should reside in the base directory 
<?xml version="1.0"?>
  <project name="Hello World Project" default="info">
  <target name="info">
     <echo>Hello World - Welcome to Apache Ant!</echo>

The XML element project has three attributes:
The Name of the project. (Optional)
The default target for the build script. A project may contain any number of targets. This attribute specifies which target should be considered as the default. (Mandatory)
The base directory (or) the root folder for the project. (Optional)

b. Ant – Jenkins Configuration

Click on Build now it will automatically deploy war in Tomcat Server
  1. Maven Project Configuration in Jenkins

  1. Maven basics

Maven is a project management and comprehension tool. Maven provides developers a complete build lifecycle framework. 
Maven provides developers ways to manage following:
  • Builds
  • Documentation
  • Reporting
  • Dependencies
  • SCMs
  • Releases
  • Distribution
  • mailing list
  • POM is an acronym for Project Object Model.
  • The pom.xml file contains information of project and configuration information for the maven to build the project such as dependencies, build directory, source directory, test source directory, plugin, goals etc.
  • Maven reads the pom.xml file, then executes the goal.
Elements of maven pom.xml file
For creating the simple pom.xml file, you need to have following elements:
It is the root element of pom.xml file.
It is the sub element of project. It specifies the modelVersion. It should be set to 4.0.0.
It is the sub element of project. It specifies the id for the project group.
It is the sub element of project. It specifies the id for the artifact (project).
An artifact is something that is either produced or used by a project.
Examples of artifacts produced by Maven for a project include:
JARs, source and binary distributions, and WARs.
It is the sub element of project. It specifies the version of the artifact under given group.

Maven pom.xml file with additional elements
Here, we are going to add other elements in pom.xml file such as:
defines packaging type such as jar, war etc.
defines name of the maven project.
defines url of the project.
defines dependencies for this project.
defines a dependency. It is used inside dependencies.
defines scope for this maven project. It can be compile, provided, runtime, test and system.

b. Maven – Jenkins Configuration