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 have covered Kubernetes and the clustering process in detail. In order to enhance this knowledge, we recommend the following exercises:

  1. Run a hello world application on the Kubernetes cluster:
    1. The hello world application can look exactly the same as the one we described in the exercises for Chapter 2, Introducing Docker
    2. Deploy the application with three replicas
    3. Expose the application with the NodePort service
    4. Make a request (using curl) to the application
  1. Implement a new feature, Goodbye World!, and deploy it using a rolling update:
    • This feature can be added as a new endpoint, /bye, which always returns Goodbye World!
    • Rebuild a Docker image with a new version tag
    • Use the RollingUpdate strategy and readinessProbe
    • Observe the rolling update procedure
    • Make a request (using curl) to the application