Basic DevOps Pipeline

Description

In this project, we will be creating a basic DevOps pipeline all the way from making a code change to deploying that change to a production environment. The change we will be making is changing the header text on our page from "DevOps is Great!" to "DevOps is Awesome!"

- Let me go over the tools we will be utilizing in this project.
GitHub: The source control repo, where the application code is stored. We will be forking the repo from https://github.com/linuxacademy/devops-essentials-sample-app

Staging & Prod Server: There will be a server for verifying and testing changes, and another simulating the production environment.

Jenkins: We will use Jenkins for the entire orchestration process of this project. Taking code from GitHub, deploying it to the staging, and then handling deployment to production.

Project walk-through:

I will start by forking the sample app repo from Linux Academy, which contains a basic HTML page that says "DevOps is Great" https://github.com/linuxacademy/devops-essentials-sample-app

Now we're going to configure the Jenkins CI server to point to the forked repo, which will scan and detect all the branches within that repo.



After making code changes, make a pull request and merge new changes to personal fork master branch, which represent code that is ready to be deployed to production.



We are now going to return back to Jenkins CI server and deploy the change. It is important to verify the changes in the staging server before confirming the deployment to production.



Thank you for following along.