Book Image

Continuous Delivery with Docker and Jenkins, 3rd Edition - Third Edition

By : Rafał Leszko
Book Image

Continuous Delivery with Docker and Jenkins, 3rd Edition - Third Edition

By: Rafał Leszko

Overview of this book

This updated third edition of Continuous Delivery with Docker and Jenkins will explain the advantages of combining Jenkins and Docker to improve the continuous integration and delivery process of app development. You’ll start by setting up a Docker server and configuring Jenkins on it. Next, you’ll discover steps for building applications and microservices on Dockerfiles and integrating them with Jenkins using continuous delivery processes such as continuous integration, automated acceptance testing, configuration management, and Infrastructure as Code. Moving ahead, you'll learn how to ensure quick application deployment with Docker containers, along with scaling Jenkins using Kubernetes. Later, you’ll explore how to deploy applications using Docker images and test them with Jenkins. Toward the concluding chapters, the book will focus on missing parts of the CD pipeline, such as the environments and infrastructure, application versioning, and non-functional testing. By the end of this continuous integration and continuous delivery book, you’ll have gained the skills you need to enhance the DevOps workflow by integrating the functionalities of Docker and Jenkins.
Table of Contents (16 chapters)
1
Section 1 – Setting Up the Environment
5
Section 2 – Architecting and Testing an Application
9
Section 3 – Deploying an Application

Exercises

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

  1. Use Flyway to create a non-backward-compatible change in the MySQL database:
    1. Use the official Docker image, mysql, to start the database.
    2. Configure Flyway with a proper database address, username, and password.
    3. Create an initial migration that creates a USERS table with three columns: ID, EMAIL, and PASSWORD.
    4. Add sample data to the table.
    5. Change the PASSWORD column to HASHED_PASSWORD, which will store the hashed passwords.
    6. Split the non-backward-compatible change into three migrations, as described in this chapter.
    7. You can use MD5 or SHA for hashing.
    8. Check that the database doesn't store any passwords in plain text as a result.
  2. Create a Jenkins shared library with steps to build and unit test Gradle projects:
    1. Create a separate repository for the library.
    2. Create two files in the library...