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've covered a lot of material in this chapter. To consolidate what we have learned, we recommend two exercises:

  1. Run CouchDB as a Docker container and publish its port:

Note

You can use the docker search command to find the CouchDB image.

    1. Run the container
    2. Publish the CouchDB port
    3. Open the browser and check that CouchDB is available
  1. Create a Docker image with the REST service replying Hello World! to localhost:8080/hello. Use any language and framework you prefer:

Note

The easiest way to create a REST service is to use Python with the Flask framework (http://flask.pocoo.org/). Note that a lot of web frameworks, by default, start the application only on the localhost interface. In order to publish a port, it's necessary to start it on all interfaces (app.run(host='0.0.0.0' in the case of a Flask framework).

    1. Create a web service application
    2. Create a Dockerfile to install dependencies and libraries
    3. Build the image
    4. Run the container that is publishing the port
    5. Check that it's running correctly...