Book Image

Continuous Delivery with Docker and Jenkins - Second Edition

By : Rafał Leszko
Book Image

Continuous Delivery with Docker and Jenkins - Second Edition

By: Rafał Leszko

Overview of this book

Continuous Delivery with Docker and Jenkins, Second Edition will explain the advantages of combining Jenkins and Docker to improve the continuous integration and delivery process of an 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 Kubernetes. Next, you will get to know how to deploy applications using Docker images and testing them with Jenkins. Towards the end, the book will touch base with missing parts of the CD pipeline, which are the environments and infrastructure, application versioning, and nonfunctional testing. By the end of the book, you will be enhancing the DevOps workflow by integrating the functionalities of Docker and Jenkins.
Table of Contents (18 chapters)
Title Page
Dedication
About Packt
Contributors
Preface
Index

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-backwards-compatible change in the MySQL database:

    1. Use the official Docker image, mysql, to start the database
    2. Configure Flyway with 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-backwards-compatible change into three migrations as described in this chapter
    7. You can use MD5 or SHA for hashing
    8. Check that as a result, the database doesn't store any passwords in plain text
  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: gradleBuild.groovy and gradleTest.groovy
    3. Write the appropriate call...