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.

Related Content you might be interested in

Current Title:

Small book image
Continuous Delivery with Docker and Jenkins
Rafał Leszko
Aug, 2017 | 332 pages
Small book image
Docker Orchestration
Randall Smith
Jan, 2017 | 284 pages
Small book image
Beginning DevOps with Docker
Joseph Muli
May, 2018 | 96 pages
Small book image
Learning Docker
Jeeva S Chelladhurai | Pethuru Raj | Vinod Singh
May, 2017 | 300 pages
Table of Contents (10 chapters)
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Piracy
Questions
Free Chapter
1
Introducing Continuous Delivery
Introducing Continuous Delivery
What is Continuous Delivery?
The automated deployment pipeline
Prerequisites to Continuous Delivery
Building the Continuous Delivery process
Summary
2
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 cleanup
Docker commands overview
Exercises
Summary
3
Configuring Jenkins
Configuring Jenkins
What is Jenkins?
Jenkins installation
Jenkins hello world
Jenkins architecture
Configuring agents
Custom Jenkins images
Configuration and management
Exercises
Summary
4
Continuous Integration Pipeline
Continuous Integration Pipeline
Introducing pipelines
Commit pipeline
Code quality stages
Triggers and notifications
Team development strategies
Exercises
Summary
5
Automated Acceptance Testing
Automated Acceptance Testing
Introducing acceptance testing
Docker registry
Acceptance test in pipeline
Docker Compose
Acceptance testing with Docker Compose
Writing acceptance tests
Exercises
Summary
6
Configuration Management with Ansible
Configuration Management with Ansible
Introducing configuration management
Installing Ansible
Using Ansible
Deployment with Ansible
Ansible with Docker
Exercises
Summary
7
Continuous Delivery Pipeline
Continuous Delivery Pipeline
Environments and infrastructure
Nonfunctional testing
Application versioning
Complete Continuous Delivery pipeline
Exercises
Summary
8
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
Exercises
Summary
9
Advanced Continuous Delivery
Advanced Continuous Delivery
Managing database changes
Pipeline patterns
Release patterns
Working with legacy systems
Exercises
Summary
Best practices

Code quality stages

We can extend the classic three steps of Continuous Integration with additional steps. The most widely used are code coverage and static analysis. Let's look at each of them.

Code coverage

Think about the following scenario: you have a well-configured Continuous Integration process; however, nobody in your project writes unit tests. It passes all the builds, but it doesn't mean that the code is working as expected. What to do then? How to ensure that the code is tested?

The solution is to add the code coverage tool that runs all tests and verifies which parts of the code have been executed. Then, it creates a report showing not-tested sections. Moreover, we can make the build fail when there is...

Previous Section
End of Section 4
Next Section