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

Exercises


We covered a lot of new material throughout this chapter, so to aid understanding, I recommend doing the following exercises:

  1. Create a Ruby-based web service, book-library, to store books:

The acceptance criteria are delivered in the form of the following Cucumber feature:

Scenario: Store book in the library
  Given Book "The Lord of the Rings" by "J.R.R. Tolkien" with ISBN number "0395974682"
  When I store the book in library
  Then I am able to retrieve the book by the ISBN number
    1. Write step definitions for the Cucumber test
    2. Write the web service (the simplest way is to use the Sinatra framework: http://www.sinatrarb.com/, but you can also use Ruby on Rails)
    3. The book should have the following attributes: name, author, and ISBN
    4. The web service should have the following endpoints:
      • POST /books to add a book
      • GET books/<isbn> to retrieve the book
    5. The data can be stored in the memory
    6. At the end, check that the acceptance test is green
  1. Add book-library as a Docker image to the Docker registry...