Book Image

Continuous Delivery with Docker and Jenkins

By : Rafał Leszko
Book Image

Continuous Delivery with Docker and Jenkins

By: Rafał Leszko

Overview of this book

The combination of Docker and Jenkins improves your Continuous Delivery pipeline using fewer resources. It also helps you scale up your builds, automate tasks and speed up Jenkins performance with the benefits of Docker containerization. This book will explain the advantages of combining Jenkins and Docker to improve the continuous integration and delivery process of app development. It will start with setting up a Docker server and configuring Jenkins on it. It will then provide steps to build applications on Docker files and integrate them with Jenkins using continuous delivery processes such as continuous integration, automated acceptance testing, and configuration management. Moving on you will learn how to ensure quick application deployment with Docker containers along with scaling Jenkins using Docker Swarm. Next, you will get to know how to deploy applications using Docker images and testing them with Jenkins. By the end of the book, you will be enhancing the DevOps workflow by integrating the functionalities of Docker and Jenkins.
Table of Contents (10 chapters)

Acceptance test in pipeline

We already understood the idea behind acceptance testing and know how to configure Docker registry, so we are ready for its first implementation inside the Jenkins pipeline.

Let's look at the figure that presents the process we will use:

The process goes as follows:

  1. The developer pushes a code change to GitHub.
  2. Jenkins detects the change, triggers the build, and checks out the current code.
  3. Jenkins executes the commit phase and builds the Docker image.
  4. Jenkins pushes the image to Docker registry.
  5. Jenkins runs the Docker container in the staging environment.
  6. Staging the Docker host needs to pull the image from the Docker registry.
  7. Jenkins runs the acceptance test suite against the application running in the staging environment.
For the sake of simplicity, we will run the Docker container locally (and not on a separate staging server). In order...