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: https://github.com/linuxacademy/cicd-pipeline-train-schedule-dockerdeploy
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!