Debashis Sahu - DevOps-3

1. Implement a Git workflow with automatic builds on commits to master (test and deploy) and develop (test only).

2. Use a Dockerfile to containerize the code, building with each GitHub push using the hshar/webapp container, with code in /var/www/html.

3. Create Jenkins Pipeline jobs to build, test, and deploy the website.

4. Ensure /home/ubuntu/config-management/status.txt on Test and Prod servers indicates Apache installation status.

5. Set up three t2.micro AWS servers:

- Server 1: Jenkins Master

- Server 2: Testing Server, Jenkins Slave.

- Server 3: Production Server, Jenkins Slave.

Setting up three servers:

server-1, server-2 and server-3 in AWS:

Jenkins installed on server-1 and accessed by Public IP on browser . The Screenshots of server nodes in Jenkins

Server-2 and Server-3 connected to Jenkins:

Agent server-2

Agent server-3

Jenkins Job-1

Build-Website which is configured as per requirement. The step by step screenshots are mentioned below:

Jenkins Job-2:

Test-Website (downstream of Build-Website) which is configured as per requirement. The step by step screenshots are mentioned below:

Jenkins Job-3:

Push-to-Prod which is configured as per requirement. The step by step screenshots are mentioned below:

Git Workflow and Automated Build

The Jenkins Jobs are set up by the following conditions:

If commit is made to master branch, test and push to prod
If commit is made to develop branch, just test the product, do not push to prod
Here, first commit is made to develop branch (screenshot below)

The develop branch is updated in git-hub (screenshots below) . After commit on git repository:

Code File:

For this automation task, webhooks set up is applied. Screenshot of the Webhook set up given below:

After the commit on develop branch, the Jenkins job: Build-Website is started (screenshots of jenkins job console is given below)

After successful build of the Build-Website job in Jenkins, the Test-Website job is executed (screenshot of Jenkins Job console is given below)

In Terminal, the docker container is created as per the requirement which was mentioned on the Dockerfile:

The Public IP address of server 2 is tested on browser. The apache2 service is running with the desired code: index.html

As per the condition for commit on develop branch, no docker container is created on Server-3 and hence no website is built here which is crosschecked on the browser (screenshots below)

no website is built: crosschecked

Now, commit is made on master branch (screenshots below)

The code is updated on git-hub (screenshots below)

The Jenkins job: Build-Website, Test-Website and Push to Prod are executed. The new docker container in Server-2 is running to confirm the testing of code (screenshots below)

The Test server: server-2 IP address tested on browser. Test job is successful (screenshot below)

The Push-to-Prod job is also successfully built on server-3. The docker container for this is running up. The details of the Dockerfile is mentioned in the terminal view (screenshot below)

Server-3 public IP is also tested on browser (screenshot below)

The successful built of the Jenkins job: Push to Prod is mentioned in below screenshot