This repository is a tutorial it tries to exemplify how to automatically manage the process of building, testing the highest coverage and deployment phases.

GITHUB URL- Click on GitHub URL to Download the Java Project.

Our goal is to ensure our pipeline works well after each code being pushed. The processes we want to auto-manage:

Just One commit and the application is deployed in Docker Container

  1. Code checkout
  2. Run tests
  3. Compile the code
  4. Run Sonarqube analysis on the code
  5. Create Docker image
  6. Push the image to Docker Hub
  7. Pull and run the image

First step, running up the services

Since one of the goals is to obtain the Sonarqube report of our project, we should be able to access sonarqube from the jenkins service. Docker compose is a best choice to run services working together. We configure our application services in a yaml file as below.


      context: sonarqube/
      - 9000:9000
      - 9092:9092
    container_name: sonarqube
      context: jenkins/
    privileged: true
    user: root
      - 8080:8080
      - 50000:50000
    container_name: jenkins
      - /tmp/jenkins:/var/jenkins_home #Remember that, the tmp directory is designed to be wiped on system reboot.
      - /var/run/docker.sock:/var/run/docker.sock
      - sonarqube

Paths of docker files of the containers are specified at context attribute in the docker-compose.yml file. Content of these files as follows.

      FROM sonarqube:6.7-alpine
     FROM jenkins:2.60.3

If we run the following command in the same directory as the docker-compose.yml file,The Sonarqube and Jenkins containers will up and run.

docker-compose -f docker-compose.yml up --build
docker ps 

CONTAINER ID        IMAGE                COMMAND                  CREATED              STATUS              PORTS                                              NAMES

06bf0758596ft55        pipeline_jenkins     "/bin/tini -- /usr..."   About a minute ago   Up About a minute>8080/tcp,>50000/tcp   jenkins

a6dh78h9fhfjk88        pipeline_sonarqube   "./bin/"           About a minute ago   Up About a minute>9000/tcp,>9092/tcp     sonarqube

GitHub configuration

We’ll define a service on Github to call the Jenkins Github webhook because we want to trigger the pipeline.Go to Settings - Integrations & services.

The Jenkins Github plugin should be shown on the list of available services as below.

Git Plugin will call jenkins webhoook to trigger jenkins pipeline.

After this, we should add a new service by typing the URL of the dockerized Jenkins container along with the /github-webhook/ path.

The URL of the  Jenkins container along with the /github-webhook/ path integration.

The next step is that create an SSH key for a Jenkins user and define it as Deploy keys on our GitHub repository.

SSH keys for user so User can perform actions on repository.

If everything goes well, the following connection request should return with a success.

PTY allocation request failed on channel 0
Hi <your github username>/<repository name>! You've successfully authenticated, but GitHub does not provide shell access.
Connection to closed.

Jenkins configuration

We have configured Jenkins in the docker compose file to run on port 8080 therefore if we visit http://localhost:8080 we will be greeted with a screen like this.

The admin password is on the specific file location mentioned.

We need the admin password to proceed to installation. It’s stored in the /var/jenkins_home/secrets/initialAdminPassword directory and also It’s written as output on the console when Jenkins starts.

jenkins      | *************************************************************

jenkins      |

jenkins      | Jenkins initial setup is required. An admin user has been created and a password generated.

jenkins      | Please use the following password to proceed to installation:

jenkins      |

jenkins      | 45638c79cecd4f43962da2933980197e

jenkins      |

jenkins      | This may also be found at: /var/jenkins_home/secrets/initialAdminPassword

jenkins      |

jenkins      | ************************************************************

To access the password from the container.

docker exec -it jenkins sh

$cat /var/jenkins_home/secrets/initialAdminPassword

After entering the password, we will download recommended plugins and define an admin user.

Admin user need to be setup for overall operations to be successfully done.

After clicking Save and Finish and Start using Jenkins buttons, we should be seeing the Jenkins homepage. One of the seven goals listed above is that we must have the ability to build an image in the Jenkins being dockerized. Take a look at the volume definitions of the Jenkins service in the compose file.


The purpose is to communicate between the Docker Daemon and the Docker Client(we will install it on Jenkins) over the socket. Like the docker client, we also need Maven to compile the application. For the installation of these tools, we need to perform the Maven and Docker Client configurations under:-

Manage Jenkins - Global Tool Configuration Menu.

A library plugin used to define common global configuration UI for Amazon Web Services.

We added the Maven and Docker installers and have checked the Install automatically checkbox.

Now we will perform checkout codebaseand pushing an image to Docker Hub,we need to define the Docker Hub Credentials.Keep in mind that if we are using a private repo,we must define Github credentials.These definitions are performed under:-

Jenkins Home Page - Credentials - Global credentials - Add Credentials menu.

Credentials stored in Jenkins can be used: anywhere applicable throughout Jenkins (i.e. global credentials)

Go to Jenkins - Credentials - System - mark env variables.

The Global Properties lets you define variables that can be managed centrally but used in all of your build .

Create a repository in docker hub so the built image is pushed to docker registry with its credentials (need to be filled in jenkinsFile)

Docker Hub is a cloud-based repository in which Docker users and partners create, test, store and distribute container images.

We use the value we entered in the ID field to Docker Login in the script file. Now, we define pipeline under:-

Jenkins home page - New item menu.

The Jenkins allow us to create new pipeline project where we can write jenkins file for our workflows.

In this step, we select GitHub hook trigger for GITScm pooling options for automatic run of the pipeline by Github hook call.

This feature enables builds after post-receive hooks in your GitHub repositories

Also in the Pipeline section, we select the Pipeline script from SCM as Definition, define the GitHub repository and the branch name, and specify the script location.

 Pipeline plugin, users can implement a project’s entire build/test/deploy pipeline in a Jenkinsfile and store that alongside their code, treating their pipeline as another piece of code checked into source control.

After that, when a push is done to the remote repository or when you manually trigger the pipeline by Build Now option, the steps described in Jenkins file will be executed.

 CI/CD bridges the gap between development and operations teams by automating build, test and deployment of applications as shown in diagram.

After that, when a Deployment is done to the remote repository and automatic trigger to pipeline by Build Now You can see the Workflow step by step .Go to Docker Login check the Images and then check the container in which the application is running.

After Deployment is done and Container is running , You can check it by URL and Port number on which the service is running.

check the URL and Port number on which the docker service is running.

Review important points of the Jenkins file


    def dockerHome = tool 'myDocker'

    def mavenHome  = tool 'myMaven'

    env.PATH = "${dockerHome}/bin:${mavenHome}/bin:${env.PATH}"


The Maven and Docker client tools we have defined in Jenkins under Global Tool Configuration menu are added to the PATH environment variable for using these tools with sh command.

stage('Push to Docker Registry'){

    withCredentials([usernamePassword(credentialsId: 'dockerHubAccount', usernameVariable: 'USERNAME', passwordVariable: 'PASSWORD')]) {




withCredentials provided by Jenkins Credentials Binding Plugin and bind credentials to variables. We passed dockerHubAccount value with credentialsId parameter. Remember that, dockerHubAccount value is Docker Hub credentials ID we have defined it under:-

Jenkins Home Page - Credentials - Global credentials - Add Credentials menu.

 Jenkins Credentials Binding Plugin and bind credentials to variables under Global Tool Configuration.

In this way, we access to the username and password information of the account for login.

Sonarqube configuration

For Sonarqube we have made the following definitions in the pom.xml file of the project.


In the docker compose file, we gave the name of the Sonarqube service which is Sonarqube, this is why in the pom.xml file, the sonar URL was defined as http://sonarqube:9000.

Things To Remember:

1 Do not forget to add environment variables in jenkins WRT to Jenkinsfile

2 Docker Hub Repository should be created and also the repository should be marked in the Variable in JenkinsFile

Docker Hub is a cloud-based repository in which Docker users and partners create, test, store and distribute container images.

JenkinsFile Configuration

def CONTAINER_NAME="jenkins-pipeline"
def CONTAINER_TAG="latest"
def HTTP_PORT="8090"

def pushToImage(containerName, tag, dockerUser, dockerPassword){

 sh "docker login -u $dockerUser -p $dockerPassword"
 sh "docker tag $containerName:$tag $dockerUser/$containerName:$tag"
 sh "docker push $dockerUser/$containerName:$tag"
 echo "Image push complete"

def runApp(containerName, tag, dockerHubUser, httpPort){

 sh "docker pull $dockerHubUser/$containerName"
 sh "docker run -d - rm -p $httpPort:$httpPort - name   $containerName $dockerHubUser/$containerName:$tag"
 echo "Application started on port: ${httpPort} (http)"

By the way, check out our best AWS deal: