Book Image

Continuous Delivery with Docker and Jenkins, 3rd Edition - Third Edition

By : Rafał Leszko
Book Image

Continuous Delivery with Docker and Jenkins, 3rd Edition - Third Edition

By: Rafał Leszko

Overview of this book

This updated third edition of Continuous Delivery with Docker and Jenkins will explain the advantages of combining Jenkins and Docker to improve the continuous integration and delivery process of app development. You’ll start by setting up a Docker server and configuring Jenkins on it. Next, you’ll discover steps for building applications and microservices on Dockerfiles and integrating them with Jenkins using continuous delivery processes such as continuous integration, automated acceptance testing, configuration management, and Infrastructure as Code. Moving ahead, you'll learn how to ensure quick application deployment with Docker containers, along with scaling Jenkins using Kubernetes. Later, you’ll explore how to deploy applications using Docker images and test them with Jenkins. Toward the concluding chapters, the book will focus on missing parts of the CD pipeline, such as the environments and infrastructure, application versioning, and non-functional testing. By the end of this continuous integration and continuous delivery book, you’ll have gained the skills you need to enhance the DevOps workflow by integrating the functionalities of Docker and Jenkins.
Table of Contents (16 chapters)
1
Section 1 – Setting Up the Environment
5
Section 2 – Architecting and Testing an Application
9
Section 3 – Deploying an Application

Chapter 4: Continuous Integration Pipeline

  1. A pipeline is a sequence of automated operations that usually represents a part of the software delivery and quality assurance process.
  2. A step is a single automated operation, while a stage is a logical grouping of steps used to visualize the Jenkins pipeline process.
  3. The post section defines a series of one or more step instructions that are run at the end of the pipeline build.
  4. Checkout, compile, and unit test.
  5. Jenkinsfile is a file with the Jenkins pipeline definition (usually stored together with the source code in the repository).
  6. The code coverage stage is responsible for checking whether the source code is well covered with (unit) tests.
  7. An external trigger is a call from an external repository (such as GitHub) to the Jenkins master, while Polling SCM is a periodic call from the Jenkins master to the external repository.
  8. Email, group chat, build radiators, sms, rss feed.
  9. Trunk-based...