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.

Preface

What this book covers

What you need for this book

Who this book is for

Reader feedback

Customer support

Free Chapter

Introducing Continuous Delivery

Introducing Continuous Delivery

What is Continuous Delivery?

The automated deployment pipeline

Prerequisites to Continuous Delivery

Building the Continuous Delivery process

Introducing Docker

Introducing Docker

What is Docker?

Docker installation

Running Docker hello world>

Docker applications

Building images

Docker container states

Docker networking

Using Docker volumes

Using names in Docker

Docker commands overview

Configuring Jenkins

Configuring Jenkins

What is Jenkins?

Jenkins installation

Jenkins hello world

Jenkins architecture

Configuring agents

Custom Jenkins images

Configuration and management

Continuous Integration Pipeline

Continuous Integration Pipeline

Introducing pipelines

Commit pipeline

Code quality stages

Triggers and notifications

Team development strategies

Automated Acceptance Testing

Automated Acceptance Testing

Introducing acceptance testing

Docker registry

Acceptance test in pipeline

Acceptance testing with Docker Compose

Writing acceptance tests

Configuration Management with Ansible

Configuration Management with Ansible

Introducing configuration management

Installing Ansible

Deployment with Ansible

Ansible with Docker

Continuous Delivery Pipeline

Continuous Delivery Pipeline

Environments and infrastructure

Nonfunctional testing

Application versioning

Complete Continuous Delivery pipeline

Clustering with Docker Swarm

Clustering with Docker Swarm

Server clustering

Docker Swarm in practice

Advanced Docker Swarm

Docker Compose with Docker Swarm

Alternative cluster management systems

Scaling Jenkins

Advanced Continuous Delivery

Advanced Continuous Delivery

Managing database changes

Pipeline patterns

Release patterns

Working with legacy systems

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

Using Ansible

In order to use Ansible, first we need to define the inventory, which represents the available resources. Then, we will be able to either execute a single command or define a set of tasks using the Ansible playbook.

Creating inventory

An inventory is a list of all the servers that are managed by Ansible. Each server requires nothing more than the Python interpreter and the SSH server installed. By default, Ansible assumes that the SSH keys are used for authentication; however, it is also possible to use the username and the password by adding the --ask-pass option to the Ansible commands.

SSH keys can be generated with the ssh-keygen tool and are usually stored in the ~/.ssh directory.

The inventory is defined...