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)

Summary

In this chapter, we have completed the Continuous Delivery pipeline, which finally releases the application. The following are the key takeaways from the chapter:

  • For the purpose of Continuous Delivery, two environments are indispensable: staging and production.
  • Nonfunctional tests are an essential part of the Continuous Delivery process and should always be considered as pipeline stages.
  • Nonfunctional tests that don't fit the Continuous Delivery process should be considered as periodic tasks in order to monitor the overall performance trends.
  • Applications should always be versioned; however, the versioning strategy depends on the type of the application.
  • The minimal Continuous Delivery pipeline can be implemented as a sequence of scripts that ends with two stages: release and smoke test.
  • The smoke test should always be added as the last stage of the Continuous Delivery...