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)

Exercises

In this chapter, we have covered various aspects of the Continuous Delivery process. Since practice makes perfect, we recommend the following exercises:

  1. Use Flyway to create a non-backwards-compatible change in the MySQL database:

    • Use the official Docker image, mysql, to start the database
    • Configure Flyway with proper database address, username, and password
    • Create an initial migration that creates a users table with three columns: id, email, and password
    • Add a sample data to the table
    • Change the password column to hashed_password, which will store the hashed passwords
    • Split the non-backwards-compatible change into three migrations as described in this chapter
    • You can use MD5 or SHA for hashing
    • Check that, as a result, the database stores no passwords in plain text
  2. Create a Jenkins shared library with steps to build and unit test Gradle projects:
    • Create a separate...