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

Summary


In this chapter, we covered the Docker basics, which is enough to build images and run applications as containers. Here are the key takeaways:

The containerization technology addresses the issues of isolation and environment dependencies using the Linux kernel features. This is based on the process separation mechanism, so therefore, no real performance drop is observed. Docker can be installed on most of the systems, but is supported natively only on Linux. Docker allows us to run applications from the images available on the internet and to build our own images. An image is an application packed together with all the dependencies.

Docker provides two methods for building the images—Dockerfile or committing the container. In most cases, the first option is used. Docker containers can communicate over the network by publishing the ports they expose. Docker containers can share the persistent storage using volumes. For the purpose of convenience, Docker containers should be named, and...