by Logo Technical Blog – Future Processing
Mateusz Chrobok
Michał Perczak
Automation of the process building and deployment multi branch web application using Jenkins, Docker and Nginx_

Inspiration to writing this article has been excerpted from the lecture “Like a Panda: Flow with Bamboo” led by Jonathan Doklovic, one of Atlassian’s employee, during Atlassian Summit 2013.

That lecture described potential of building and deploying feature branches. Such functionality is offered by Bamboo – software released by Atlassian itself.

Atlassian Summit 2013: Like a Panda: Flow with Bamboo

Owing to the fact that the team was approaching a new project, which by definition should have a didactic element, it was decided to prepare similar solution using other, free CI tool. The choice was Jenkins, widely known and used in IT projects.


A short list of features, which should be supported by new solution, had been prepared before the project started.

  • changes introduced into repository should be immediately available for the QA team and other stakeholders
  • the whole process is automatic, except for elements which were declared as manual steps
  • deployment of changes introduced to feature branches should give opportunity to test features in isolation (before code is merged to the master branch)
  • solution is reusable and it is possible to use it in subsequent projects

How does it work?

How does it work - Future Processing

A sample flow:

  1. Development process
    1. A developer starts working on a new User Story named “Create login page” with issue number 3 within a XYZ project.
    2. A developer creates new branch “XYZ-3-Create-login-page
    3. A developer introduces some changes and pushes branch to repository
    4. Jenkins creates new job with name “XYZ-3-Create-login-page
    5. Jenkins runs newly created job
    6. Launched job creates Docker image with tag “XYZ-3-Created-login-page
    7. Launched job runs container from newly created image
    8. Nginx notes launched container and creates subdomain “XYZ-3
  2. Testing feature in isolated environment
    1. A QA gets notification that changes related to User Story have been deployed
    2. A QA uses “” URL in order to access introduced changes
    3. A QA checks correctness of solution in isolation, before merging to master branch
  3. Merge changes
    1. A developer merges his branch to master branch
    2. A developer removes branch related to his User Story
    3. Jenkins removes job related to User Story
  4. Deploy staging environment
    1. Jenkins runs build related to master branch
    2. Launched build creates Docker image with tag “0.1.0-SNAPSHOT
    3. Launched build runs container from newly created image
    4. Nginx notes launched container and creates subdomain “staging
  5. Testing feature in staging environment
    1. A QA gets notification that changes related to master branch have been deployed
    2. A QA uses “” URL in order to access introduced changes
    3. A QA checks correctness of solution after merge changes to master branch


Solution assumes that two kind of branches exist in repository:

  • master – the main branch
  • feature – a branch of this type is related to one specific User Story

It is not required to work with full featured git-flow. Nothing prevents use of some other branching concepts. The only requirement is to have the branches mentioned above. Other branches, from solution perspective, don’t matter. Jobs in Jenkins are related only to master and feature branches.

Feature branches are typical ones, however logically they play a different role. Some mechanism is needed to distinguish them from other branches. In order to do that, some naming convention is required. For such project like XYZ, feature branches can be named in that way:

-[User Story number]-[name of User Story]

Regular expression which is needed to distinguish branches from feature branches is required to be introduced in Jenkins job.

A sample structure of branches in a fake project XYZ - Future Processing

The illustration above depicts a sample structure of branches in a fake project XYZ. For such structure the following URLs are available:

  • – URL related to the last tag 0.1.0
  • – URL related to the current state of master branch
  • – URL related to the current state of User Story “Login Page”
  • – URL related to the current state of User Story “Payments Details”
  • – URL related to the current state of User Story “Groups”

Domain “” is not configurable. It depends on external settings.


When configuring Jenkins, few plugins have been applied in order to achieve desired shape:

  • Environment Injector Plugin
  • GIT plugin
  • Multi-Branch Project Plugin
  • SSH Agent Plugin
  • Maven Release Plugin

Docker image has been used in order to setup Jenkins and one slave node.

Jenkins, configured for this solution, contains 4 jobs. Their description with sketch is presented below. Important elements are marked with red border.

Job XYZ - Future Processing


XYZ is a template job formed by Multi-Branch Project Plugin which allows to:

  • detect branches which match against regular expression
  • create job if corresponding branch appears in repository
  • remove job if corresponding branch is removed from repository
  • launch job if changes are introduced to that branch

Multibranch job specifies time interval when and which job template instances synchronize with corresponding branches. In the example shown below, branches synchronize every 2 minutes. Only these branches, which names do not match against “tasks/*” and “master” patterns, are tracked. Each time, when changes are introduced to these branches, Jenkins detects changes and performs appropriate action.

Jenkins - Source Code Management - Future Processing

When Jenkins launches job related to specific branch, the script shown below is executed at first. From branch name, which is given in GIT_BRANCH variable, only some part is extracted (as described in “Git” section). Output string is stored in a file “” as variable FEATURE, which is injected in the subsequent step.

Jenkins - Build Environment - Future Processing

Jenkins - Build - Future Processing

At the end, Maven command is invoked. Two profiles are specified to be launched. Moreover, two parameters are passed.

  • environment – a constant which is always equal “dev”
  • tag – a string created as described in the section “Git” i.e. “XYZ-100”

Jenkins - Invoke top-level Maven targets - Future Processing

An image-build profile launches script which is responsible for creating Docker image. Image is formed based on Dockerfile, which is presented below. JAR file with compiled application is copied to appropriate directory and port 8080 is exposed. When Docker launches a container an application automatically starts.

This Dockerfile is used by script, which is executed by an image-build profile.

FROM java:openjdk-8-jre
COPY facebook-recruitment.jar /home/facebook-recruitment/
ENTRYPOINT ["java", "-jar", "/home/facebook-recruitment/facebook-recruitment.jar"]

Firstly, some parameters received from Jenkins are gathered in one place. Then, an image is built and pushed to the local image repository. In order to keep everything clean, the image is removed from machine where it was created.


docker -H $HOST_BUILD build -t $IMAGE_NAME .
docker -H $HOST_BUILD push $IMAGE_NAME

When an image is pushed to repository, image-deploy profile is launched. Main goal is to execute script

At the beginning, a script gathers parameters received from Jenkins. For feature branches, an image tag is equal to variable calculated by script launched in Jenkins e.g. “XYZ-100”. Docker container inherits this name in order to simplify identification which container belongs to which user story. In the next step VIRTUAL_HOST environment variable is created. More details about that variable can be found in the “Nginx” section. At the end, Docker removes existing container (if one is currently running), pulls an image from image repository and lunches container.



if [ $ENVIRONMENT = "dev" ]
elif [ $ENVIRONMENT = "staging" ]
   PORT_CONFIG="-p 80:8080"


As a result, the following things are obtained:

  • an image for specific User Story in local image repository
  • an application is deployed at https://
    -[User Story number]

Job XYZ Staging - Future Processing

Job XYZ Staging

XYZ Staging is quite similar to the template job described above. It is not a template and it is much simpler. Job is launched automatically, just after Jenkins detects changes in the master branch. The Maven command is executed within that job.

clean deploy -Pimage-build,image-deploy -Dtag=${project.version} -Denvironment=staging

Similarly, “image-build” and “image-deploy” are invoked during the Maven process.

  • environment – a constant which is always equal to “staging”
  • tag – equal to the current application version which is hardcoded in pom.xml e.g. 0.1.0-SNAPSHOT.

As a result, the following things are obtained:

  • an image with tag -SNAPSHOT in local image repository
  • an application deployed at

Job XYZ Release - Future Processing

Job XYZ Release

XYZ Release is manual job used for creating new releases. Maven Release Plugin is used in order to perform 3 operations:

  • update version in pom.xml (i.e. from 0.1.0-SNAPSHOT to 0.1.0) and commit changes
  • create tag with newly updated version
  • update version in pom.xml to new SNAPSHOT (i.e. from 0.1.0 to 0.2.0-SNAPSHOT) and commit changes

Job is parametrized, so a developer has to specify stable and next snapshot version. A number of stable versions is also used as image tag. Only “image-build” profile is launched within XYZ Release.

Jenkins - Perform Maven Release - Future Processing

-Dresume=false release:prepare release:perform -DreleaseProfiles="image-build" -Darguments="-Dtag=$MVN_RELEASE_VERSION"

As a result, the following things are obtained:

  • an image with tag in local image repository
  • an image with tag -SNAPSHOT in local image repository

Job XYZ Deploy - Future Processing

Job XYZ Deploy

XYZ Deploy is simple job used to deploy any created image to production environment. Usually, the newest image should be deployed. Job is parametrized, so a developer has to specify image tag to deploy.

Jenkins - Tag - Future Processing

The script listed below is executed

cd <path_to_deploy.sh_script>
./ $TAG production

As a result, the following things are obtained:

  • an application deployed at


In the presented solution several goals are developed:

  • an application should be easily and quickly available to QA Team
  • an application should include only changes from related User Story
  • an application with changes from specific User Story should be launched immediately in isolation

This feature description might rise a few questions:

Q: What exactly does it mean “easily and quickly available to the QA Team”?
A: Access to application will be via link that should be easy to remember and uniquely identify a User Story.

Q: What exactly does it mean “easy to remember URL”?
A: URL will be descriptive for the QA Team and should be generated automatically according to predictable convention.

Q: What exactly does it mean “URL will be descriptive”?
A: The most descriptive for QA Team are user story JIRA’s code name e.g. XYZ-9

All answers for these questions can be found in the post written by Jason Wider: Automated Nginx Reverse Proxy for Docker. That solution seems to match mentioned assumptions. In this post Jason described how Nginx can be used as Reverse Proxy and how it is possible to use virtual host for routing between docker containers. In our case special docker image named nginx-proxy based on Nginx has been prepared. Image groups Docker containers with application by environment variable VIRTUAL_HOST. After such Nginx a container is launched, all containers with that variable are able to be accessed via appropriate subdomain. More information can be found in the post mentioned above. All steps which are needed for implementation are listed below:

  • launch Jason’s Docker image on a machine which should host applications related to specific feature brunches. It is possible to achieve it by invoking the following command:
    docker run -d -p 80:80 -v /var/run/docker.sock:/tmp/docker.sock:ro jwilder/nginx-proxy

    Parameter -v /var/run/docker.sock:/tmp/docker.sock causes that launched Docker image has access to Docker API. It gives possibility to check other containers on the same machine in order to localize the ones, which have VIRTUAL_HOST environment variable

  • launch Docker container which includes web application and set variable VIRTUAL_HOST in a proper way e.g. It is possible to achieve it by invoking command in script:
    docker run -d --restart=always --name $CONTAINER_NAME -e VIRTUAL_HOST=$SUBDOMAIN $IMAGE_NAME

    Jenkins as Docker container it is problematic to access launched application containers on another machine. Access from Docker container to another machine is possible by -H parameter. Such parameter allows to access Docker daemon which constantly listens on port 2375. The full command is presented below:

    docker -H $HOST_DEPLOY:2375 run -d --restart=always --name $CONTAINER_NAME -e VIRTUAL_HOST=$SUBDOMAIN $IMAGE_NAME

In presented approach one thing is very important. The containers that are proxied must expose the port to be proxied, either by using the EXPOSE directive in their Dockerfile or by using the –expose flag. In presented solution variable EXPOSE is configured in dockerfile:

FROM java:openjdk-8-jre
COPY facebook-recruitment.jar /home/facebook-recruitment/
ENTRYPOINT ["java", "-jar", "/home/facebook-recruitment/facebook-recruitment.jar"]

After these steps an application should be available on the address which was passed by VIRTUAL_HOST parameter. Sketch of that approach is presented below:

Nginx - Future Processing


Created solution performed well in the conducted project. However, there are some things that could be created and some, which require further improvements. All these things have been listed below:

  • Notifications about successful deployment of feature branch
    In the current shape, Jenkins informs only about build failure by sending appropriate email. It is a standard behaviour, which forces developer to introduce required fixes to make the build stable. However, there is not information that feature branch has been successfully deployed. To solve that problem, creating proper comments in Jira issues would be beneficial. Jira Issue Updater Plugin offers such functionality. Comment could contain a list of mentioned people and URL address which redirects to newly deployed version of application.
  • Automatic removal of existing Docker containers
    Environment, which has been created for specific User Story, has to be removed manually. Multi-Branch Project Plugin detects only when branch is created or removed. It does not give possibility to trigger any custom action when such event occurs. It means that some scheduling mechanism has to be setup to remove environments which are not needed anymore (because related branches are removed)
  • Docker images backup
    Because of images size they are stored in local image repository. It helps to reduce time for uploading/downloading such images. Unfortunately, there is no backup mechanism.
  • Reusability
    The resulting solution only seems to be reusable. Unfortunately, subsequent projects revealed that many things were not well thought out. Solution has been created for stateless project, without any database. In the subsequent projects some changes would be required to create new database for every User Story. Some data initialization would be beneficial for testing purposes. Moreover, problem occurs when it is require to pay for each environment created for feature branch. A project, which is developed and hosted using e.g. AWS, will consume large amount of money.

Related Posts



This website stores cookies on your computer. These cookies are used to improve our website and provide more personalized services to you, both on this website and through other media. To find out more about the cookies we use, see our Cookies policy.