Skip to content

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.
  • Labs icon Lab
  • A Cloud Guru
Google Cloud Platform icon

Deploying a Docker Container with Jenkins Pipelines

Docker is a great tool for containerization. However, there are some problems that need to be solved when transitioning from a Jenkins Pipeline deployment that uses code artifacts to one that uses Docker. This learning activity will guide you through the process of deploying an app as a Docker container using a Jenkins Pipeline. After completing this exercise, you will have the knowledge necessary to Dockerize applications while still maintaining automated deployment with Jenkins Pipelines.

Google Cloud Platform icon

Path Info

Clock icon Intermediate
Clock icon 1h 30m
Clock icon Jul 08, 2018

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.

Table of Contents

  1. Challenge

    Configure Jenkins to run the new dockerized train-schedule pipeline

    To accomplish this, you will need to do the following setup in Jenkins:

    1. Configure Jenkins credentials for the production server:
    2. Using the cloud_user password, create a Jenkins credential called deploy.
    3. Configure Jenkins credentials for the Docker image registry (Docker Hub).
    4. Create a Jenkins credential called docker_hub_login. You will need a docker hub account in order to perform this step.
    5. Configure a global property in Jenkins to store the production server IP.
    6. Create a global property in Jenkins called prod_ip and set it to the Production Server Public IP that appears on the learning activity page once the servers are started up.
    7. Create a multibranch pipeline project in Jenkins called train-schedule.
    8. Configure the Jenkins project to pull from your fork of the source code.
    9. Make a fork of the Git repo at:
  2. Challenge

    Successfully deploy the train-schedule app to production as a Docker container using the Jenkins Pipeline

    1. Implement the following new stages in the Jenkinsfile:
    • Build Docker Image: Build a Docker image with the runnable code inside it.
    • Push Docker Image: Push the image to Docker Hub.
    • DeployToProduction: Deploy the new image to production.
    • Stop and remove any older containers.
    • Pull and run the newly built image.
    1. After implementing these stages, run the build in Jenkins to deploy the application to production!

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

What's a lab?

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Provided environment for hands-on practice

We will provide the credentials and environment necessary for you to practice right within your browser.

Guided walkthrough

Follow along with the author’s guided walkthrough and build something new in your provided environment!

Did you know?

On average, you retain 75% more of your learning if you get time for practice.

Start learning by doing today

View Plans