All courses
Resource hub
Featured resource
Tech Upskilling Playbook 2025
Tech Upskilling Playbook

Build future-ready tech teams and hit key business milestones with seven proven plays from industry leaders.

Learn more
Hamburger Icon
  • Labs icon Lab
  • Cloud
Google Cloud Platform icon
Labs

Implementing Fully-Automated Deployment in a CD Pipeline

Many companies that practice continuous deployment use a hands-free, fully-automated deployment model. This allows them to ship code to production with various automated tests and sanity checks built into the process, bypassing the need for human intervention. In this lesson, you will implement a basic sanity check and see a simple fully-automated deployment pipeline in action. This will give you a hands-on introduction to the concept of fully-automated deployments.

Get started Contact sales
Google Cloud Platform icon
Labs

Path Info

Level
Clock icon Intermediate
Duration
Clock icon 1h 30m
Last updated
Clock icon Aug 30, 2025

Contact sales

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

Table of Contents

  1. Challenge

    Prepare the Jenkins environment and verify your configuration with an initial deploy.

    To accomplish this, you will need to do the following steps:

    • Fork the sample source code at: https://github.com/ACloudGuru-Resources/cicd-pipeline-train-schedule-autodeploy
    • Change the DOCKER_IMAGE_NAME at the top of the Jenkinsfile to use your Docker Hub username instead of willbla.
    • Log in to Jenkins.
    • Add Jenkins credentials for GitHub, Docker Hub, and the Kubernetes cluster.
    • Set up automatic GitHub hook management in Jenkins.
    • Create a train-schedule project to build from your GitHub fork, and configure it to trigger automatically using a webhook.
    • Successfully run, approve, and deploy a build.

  2. Challenge

    Add a smoke test with automated deployment and remove the human approval step from the pipeline, then deploy.

    Do these steps to complete this:

    • Create a Jenkins environment variable called KUBE_MASTER_IP and set it to the Kubernetes master public IP.
    • Add a smoke test to verify that the canary deployment is responsive.
    • Remove the human input step from the deployment.
    • Merge the code from the new-code branch into your master branch to initiate an automated deployment.
Pluralsight Skills - Labs - Pluralsight
Author
Pluralsight Skills

Pluralsight Skills gives leaders confidence they have the skills needed to execute technology strategy. Technology teams can benchmark expertise across roles, speed up release cycles and build reliable, secure products. By leveraging our expert content, skill assessments and one-of-a-kind analytics, keep up with the pace of change, put the right people on the right projects and boost productivity. It's the most effective path to developing tech skills at scale.

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.
Ready to get started?
View individual plans View team plans