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

Jenkins Hello World


Everything in the entire IT world starts with the Hello World example, to show that the basics work fine. Let's follow this rule and use it to create the first Jenkins pipeline:

  1. Click on New Item:
  1. Enter hello world as the item name, choose Pipeline, and click on OK:
  1. There are a lot of options. We will skip them for now and go directly to the Pipeline section:
  1. Then, in the Script text-box, we can enter the pipeline script:
pipeline {
     agent any
     stages {
          stage("Hello") {
               steps {
                    echo 'Hello World'
               }
          }
     }
}
  1. Click on Save.
  2. Click on Build Now:

We should see #1 under the Build History. If we click on it, and then on Console Output, we will see the log from the pipeline build:

You have just seen the first example, and its successful output means that Jenkins is installed correctly. Now, let's see the possible Jenkins architecture.

Note

We will describe more on the pipeline syntax in Chapter 4, Continuous...