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

Chapter 3: Configuring Jenkins


  1. Yes and the image name is: jenkins/jenkins
  2. A  Jenkins master is the main instance that schedules tasks and provides the web interface, while a Jenkins agent (slave) is the additional instance that's only dedicated to executing jobs.
  3. Vertical scaling means adding more resources to the machine while the load increases. Horizontal scaling means adding more machines while the load increases.
  4. SSH and Java Web Start.
  5. A Permanent Agent is the simplest solution, and it means creating a static server with all the environment prepared to execute a Jenkins Job. On the other hand, a Permanent Docker Agent is more flexible; provides the Docker Daemon, and all the jobs are executed inside Docker containers.
  6. In the case that you use Dynamically Provisioned Docker agents and the standard ones (available on the internet) do not provide the execution environment you need.
  7.  When your organization needs some templated Jenkins to be used by different teams.
  8.  Blue Ocean is a Jenkins plugin that provides a more modern Jenkins web interface