**Copy the public IP address of the CI server provided on the lab page, and paste it into a new browser tab with :8080 appended to the end**.
In this hands-on lab, you will create a DevOps pipeline all the way from making a code change to deploying that change to a production environment. One of the great benefits of DevOps comes from its focus on automated pipelines, and here you will have the opportunity to try one out so you can see it in action from a hands-on perspective. After completing this hands-on lab, you should have a basic idea of what it is like to use a DevOps pipeline to change the code and get those changes into production.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Execute the initial deployment.
To accomplish this, create a pull request from the "new-feature" branch to "master" and merge it. Then, run the Jenkins build for the master branch. When the build reaches the "DeployToProd" stage, hover over it and click "Proceed."
This will cause the text on the production site to change from ‘DevOps is great!’ to ‘DevOps is awesome!’
- Run the “broken” deployment.
To accomplish this, create a pull request from the "broken-feature" branch to "master" and merge it. Then, run the Jenkins build for the master branch. When the build reaches the "DeployToProd" stage, hover over it and click "Proceed."
This will cause the text on the production site to change from ‘DevOps is awesome’ to ‘DevOps is awesbfgdsfkjh!’
- Roll back the broken deployment.
To do this, click on the build that you used to deploy the new-feature branch successfully, then click on "replay," and then "Run." When the build reaches the "DeployToProd" stage, hover over it and click "Proceed."
This will cause the text on the production site to change from ‘DevOps is awesbfgdsfkjh!’ back to ‘DevOps is awesome!’
