Step by Step DevOps Project on AWS - Jenkins, Terraform, Git

Learn Jenkins characteristics, features, and build infrastructure, install and configure Jenkins on an EC2 instance, then explore the GUI and create freestyle jobs.

Jenkins is an open source automation server that orchestrates build automation and pipelines, breaking large work into phases like builds, packaging, testing, and deployment.

Create an EC2 instance role for the Jenkins server, grant administration access, name the role Jenkins admin, and prepare to configure an associated security group in the next lab.

Create and configure a security group for an EC2 instance by adding inbound rules for 8080 (jenkins), 80/85 (java app), and ssh, using the same group to simplify setup.

Launch Amazon Linux t2 medium ec2 instance to run a Jenkins server, assign the Jenkins security group and instance role, configure a key pair for ssh, and verify ip addresses.

Connect to your EC2 instance using the Jenkins bin file via SSH, learn about IP changes after restarts, and preview Jenkins setup in the next lab.

Increase lab snapshot readability by zooming Google Sheets to 150–200%, and use the Google Word documents outline view to jump between steps; post issues in the forum.

Install Jenkins on an EC2 instance by provisioning Java, adding the Jenkins repo and keys, installing and starting Jenkins, retrieving the admin password, and setting up plugins and admin user.

Configure Jenkins global tools by adding the JDK with a valid Java home and installing Maven from Apache version 3.63, using the uppercase alias M three for pipelines.

Install git on the Jenkins server and add the GitHub.com host to the known hosts as Jenkins user, ensuring smooth checkout from GitHub.

Stop an EC2 instance without terminating it, verify it is stopped, then restart it and adapt to the new public IP for SSH access.

Learn a high-level tour of the Jenkins dashboard, logging in, connecting to GitHub, creating pipelines and freestyle projects, and managing plugins, credentials, and system settings.

Configure Jenkins jobs to build upstream and downstream pipelines using freestyle jobs, post build actions, and build triggers, and integrate these actions with Jenkins files.

Recreate three Jenkins jobs, including a freestyle job and two copied-from-option jobs, in this section's step-by-step labs, then create downstream and upstream jobs.

Organize your Jenkins jobs with views to group test, build, deployment, and packaging tasks, using regular expressions and naming conventions to display freestyle jobs for quick status checks.

Create a Jenkins view that includes all your freestyle jobs with a step-by-step tutorial, and post any issues on the forum for help.

Explore Jenkins pipelines and implement the phase one job of the multi-job pipeline in section three.

Define Jenkins pipelines by stages, steps, and post actions, and manage them as code using Jenkins files in Git repositories.

Create your first GitHub repository from your local machine, run the application locally, and then run it from your Jenkins server.

Create your first Jenkins workflow by initializing a local git repo, configuring SSH access to a new GitHub repository, and pushing the pet clinic spring project after key setup.

Run the Spring Petclinic app locally by packaging with Maven, launching the jar, and verifying it runs on localhost:8085 before integrating with Jenkins.

Learn to run the pet clinic application from a Jenkins pipeline, configure credentials and deployment keys, connect Jenkins to GitHub, and troubleshoot build issues with console output.

Explore how a Jenkinsfile orchestrates a multi-stage pipeline for a petclinic spring demo, declaring Maven and POM properties, tracking artifacts, and sharing build info via a properties file.

Create a base image with the latest packages and Java version for the Petclinic app. Then build an AMI-based RMI image from the Java jar from phase one using Packer.

Learn how Packer creates fully baked AMI images for AWS EC2, using templates, variables, builders, and provisioners to automate base images with Java 11 and the Petclinic app.

Install Packer on your Jenkins EC2 instance by downloading the executable, unzipping it, moving it to /usr/local/bin, and verifying the 1.8 version.

Download, unzip, and curate the petclinic package files, then initialize a git repo and push to a new private GitHub repository as the package source for building the ami.

Create a base image with ubuntu, java 11, and updated packages using packaging configuration, then pair it with the pet clinic image in a packer-driven devops pipeline.

Launch and prepare an Ubuntu EC2 micro instance, install Java, update packages, and create a base AMI for Java apps, then plan to use the AMI with Packer and Jenkins.

Learn to build a Packer image by copying the pet clinic jar into a base image, validating and building it on AWS, then launching and terminating the instance.

Explore the petclinic package demo repo and how Jenkins and Packer automate building an Amazon AMI from a base Ubuntu image, with provisioners, scripts, and a Petclinic service.

Copy the packer file to the Jenkins server, SSH in, unzip, move it to /usr/local/bin, and verify the installation.

Add the packer job to Jenkins by installing the copy artifact plugin and configuring a Git-based packaging pipeline that builds an ami and copies artifacts between jobs.

Add the Petclinic packaging job to a Jenkins multi-job pipeline using the Blue Ocean plugin, creating a visual build and packaging flow for the Petclinic app.

Build the phase three deployment using Terraform and AWS to provision an EC2 instance from a Packer image and run Petclinic tests.

Define and manage infrastructure as code with TerraForm using a declarative language. Integrate TerraForm into DevOps pipelines to automate provisioning, configuration, and destruction across multiple providers.

Explore Terraform's role in DevOps pipelines and cloud environments. Learn Terraform language concepts: data types, providers, resources, variables, file extensions (tf, tfvars), state, and commands init, plan, apply.

Explore Terraform language as a high-level, non-procedural tool that decouples resources via IDs and providers. Master data sources, resources, variables, and the init, plan, apply, destroy workflow.

Install Terraform on an Ubuntu workstation by downloading the zip, unzipping it, moving the binary to /usr/local/bin, and verifying version 1.37.

Install and configure the pet clinic exploratory repo by creating a private GitHub repo, generating SSH keys, linking via deploy keys, and pushing files for Jenkins-driven testing.

Run and validate Terraform infrastructure locally, provisioning an EC2 instance with a fully baked AMI and petclinic, while integrating manual scripts into a Jenkins pipeline for automation.

Install Terraform on the Jenkins server via scp from your local machine to the EC2 host, extract, and place it in /usr/local/bin to enable exploratory jobs.

Update Jenkins file with your GitHub repo URL, credentials ID, and main branch; replace VPC ID, install Terraform, and configure your EC2 key pair to run the petclinic project.

Pull the exploratory testing repo from GitHub into Jenkins, configure credentials and deploy keys, and add the exploratory job to the Petclinic pipeline while validating Terraform provisions for EC2.

Add the Petclinic exploratory job to a Jenkins multi-job pipeline, integrating build, packaging, and exploratory testing into a complete automated workflow with Open Blue Ocean visualization.

Learn how to integrate Jenkins with JMeter to automate API testing on AWS, deploying EC2 instances with Terraform, collecting results, and running multiple tests concurrently in a multi-job pipeline.

Explore JMeter, an open source tool to simulate heavy loads, test performance and API testing, using thread groups, controllers, listeners, timers, and assertions, and learn its integration into DevOps pipelines.

Install jmeter on a Windows local machine by downloading the zip, extracting it, navigating to the bin folder, and running the jmeter.bat file while keeping the command window open.

Install JMeter on your ubuntu workstation or terminal, copy the downloaded zip, unzip, reorganize into a JMeter directory, and place it in /usr/local/bin for easy access, then test the script.

Set up the PetClinic API repo on GitHub by creating the API directory from the downloaded zip, initializing a local git repository, committing, and pushing via SSH keys.

Create a JMeter API test and demonstrate automatic execution in DevOps pipelines, using a test plan with variables and HTTP requests for GET and POST on Petclinic.

Create a JMeter API test from scratch by configuring a test plan, variables, HTTP request samplers for GET and POST, and assertions for responses.

Run API tests from a Jenkins pipeline using JMeter on a local PC, automate test plan execution, collect CSV results, and generate an HTML report for the Petclinic API.

Explore Jenkins pipeline for api testing that provisions an ec2 with Terraform, updates the JMeter test plan with the ip, runs tests, and generates html reports before destroying the environment.

Install JMeter on the Jenkins server by securely copying the JMeter zip from Windows, unzip, rename the directory to jmeter, and move it to /usr/local/bin, then verify with jmeter -h.

Migrate the petclinic api job to a Jenkins pipeline, configure credentials and ssh keys, update jmeter tests for the ip, deploy and run api tests, and generate html reports.

Add the Petclinic API Java to a Jenkins multi-job pipeline, configure parallel API and exploratory tests after packaging, and manage executor capacity to run multiple jobs concurrently.

Integrate jmeter performance tests into a Jenkins-driven devops pipeline using Terraform to provision AWS infrastructure. Modify API tests for performance and run three phase three jobs in parallel.

Create a pet clinic performance test repository and configure a jmeter-based performance test with 100 users, initialize git, commit, and push to GitHub, managing SSH keys and deployment keys.

Modify existing API tests with JMeter to create a performance test by simulating 100 users for 30 seconds. Save and move the test plan for Jenkins integration.

Review the Petclinic performance demo repo; run a 100-user, 30-second test, update the Jenkins url and VPC ID, replace Jenkins keys, and ensure jmeter and Terraform are installed.

Set up and run a Jenkins-based performance test by creating a pipeline, configuring SSH deploy keys, linking GitHub, and deploying with Terraform to generate and validate a Petclinic performance report.

Add the performance test as the final job in a Jenkins multi-job pipeline, enabling three jobs to run in parallel and observe deployment, testing, and performance results.