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 all aspects of the Continuous Integration pipeline, which is always the first step for Continuous Delivery. Here are the key takeaways:

The pipeline provides a general mechanism for organizing any automation processes; however, the most common use cases are Continuous Integration and Continuous Delivery. Jenkins accepts different ways of defining pipelines, but the recommended one is the declarative syntax. The commit pipeline is the most basic Continuous Integration process and, as its name suggests, it should be run after every commit to the repository.

The pipeline definition should be stored in the repository as a Jenkinsfile. The commit pipeline can be extended with the code-quality stages. No matter the project build tool, Jenkins commands should always be consistent with the local development commands.

Jenkins offers a wide range of triggers and notifications. The development workflow should be carefully chosen inside the team or organization because...