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

Practice 1 – own process within the team!


Own the entire process within the team, from receiving requirements to monitoring the production. As once said: 

A program running on the developer's machine makes no money.

 This is why it's important to have a small DevOps team that takes complete ownership of a product. Actually, that is the true meaning of DevOps: Development and Operations, from the beginning to the end:

  • Own every stage of the Continuous Delivery pipeline: how to build the software, what the requirements are in acceptance tests, and how to release the product.
  • Avoid having a pipeline expert! Every member of the team should be involved in creating the pipeline.
  • Find a good way to share the current pipeline state (and the production monitoring) among team members. The most effective solution is big screens in the team space.
  • If a developer, QA, and IT Operations engineer are separate experts, then make sure they work together in one agile team. Separate teams based on expertise result in no one taking responsibility for the product.
  • Remember that autonomy given to the team results in high job satisfaction and exceptional engagement. This leads to great products!