Advanced CI/CD Pipeline with DevOps Tools

Level:Advanced

Time:3-5 hours

Cost:medium

Works locally:No

Cloud creds:Yes

Cleanup:No

Reviewed:2026-05-30

Validation:mvn -q -DskipTests=false test

Java Maven Docker Kubernetes SonarQube AWS Jenkins

Overview

Pipeline lab with Jenkins, Kubernetes manifests, and security tooling.

What You Will Build

Outcome Passing pipeline run plus scan/deploy evidence

Tools used Java, Maven, Docker, Kubernetes, SonarQube, AWS, Jenkins

Best fit Advanced - 3-5 hours

Architecture Diagram

Student workstation Repository files CI/CD pipeline AWS account Validation proof

Prerequisites

• Install or review: Java, Maven, Docker, Kubernetes, SonarQube, AWS, Jenkins.
• Use your own cloud account credentials and keep them out of commits.
• This project expects cloud resources, so verify budget alerts and cleanup first.
• Open the safety guide before running commands that create infrastructure.

Credentials And Cost Warning

Cost and credential stance

Cost risk is medium. Cloud target: AWS. Cloud credentials needed: Yes. Always use your own account, never commit secrets, and confirm cleanup before creating paid infrastructure.

Step-By-Step Lab

Use this flow before you run commands:

1. Read the cost and credential warning above.
2. Review the validation, troubleshooting, cleanup, and portfolio proof sections below.
3. Follow the original project guide preserved near the bottom of this page.
4. Return to the validation and cleanup checks before you capture portfolio evidence.

Validation Checks

Run the project validation command before and after meaningful changes:

mvn -q -DskipTests=false test

Troubleshooting

• Run mvn -q -DskipTests=false test first so local tooling issues are visible early.
• If a command fails, check tool versions, working directory, and required environment variables.
• For cloud failures, confirm account identity, region, quotas, and least-privilege IAM.
• For pipeline failures, check repository secrets, runner permissions, and pinned action versions.

Cleanup

No dedicated cleanup command was detected in the project README. Treat this as a warning: before provisioning anything, write down the exact delete, destroy, or rollback steps for your environment.

Portfolio Proof

• Validation command output: mvn -q -DskipTests=false test
• Screenshot or terminal proof: Passing pipeline run plus scan/deploy evidence
• Notes explaining what changed, what failed, and how you fixed it
• Cleanup evidence, especially for cloud or Kubernetes resources

Original Project Guide

The original README content is preserved here for lab-specific commands and context. Headings are intentionally demoted so the page outline stays focused on the standard lab flow.

External image reference devops

These are the steps I followed in the implementation of the entire CI/CD Pipeline.

🛡️ 2026 DevSecOps Enhancements (What You Will Learn)

This repository has been upgraded from a standard CI/CD deployment into a modern DevSecOps pipeline. When reviewing the Dockerfile and Jenkinsfile integrations, note the following 2026 security practices:

1. Unprivileged Container Execution: We explicitly block the Java microservice from running as a highly-privileged root user. Instead, the Dockerfile builds an isolated appuser group on a minimal Alpine Linux distribution to run the JAR file.
2. Container Immutable Deployments: We avoid overwriting the latest tag in our JFrog repository. Each successfully built artifact receives a unique semantic tag, ensuring Kubernetes deployments are rolling and easily rollback-able.

---

1. Provisioned the required infrastructure like VPC, Security Group, Ansible Controller Instance, Jenkins Master and Agent Instances using Terraform.

2. Configured SSH keys for password less authentication between Ansible Controller and Agent nodes.

3. Configured the Jenkins Master and Agent nodes using Ansible. Configured Jenkins Agent as the Maven Build server.

4. Added Jenkins Agent node’s credentials in Jenkins Master to establish a connection between Jenkins Master and Agent nodes.

5. Added GitHub credentials to the Jenkins Master and created Multibranch Pipeline job.

6. Configured the Multibranch Pipeline job with GitHub Webhook Trigger with the help of Multibranch Scan Webhook Trigger Plugin.

7. SonarQube:

   1. Generated an access token in SonarCloud and added SonarQube server credentials in Jenkins Master.
   2. Installed Sonarqube scanner plugin.
   3. Added Sonarqube server to the Jenkins Master in System section.
   4. Added Sonarqube scanner to the Jenkins Master in Tools section.
   5. Configured an organization and project in SonarCloud and wrote a sonar-project. properties file.
   6. Added sonarqube, unit tests and build stages in the Jenkinsfile.

8. Added JFrog credentials in the Jenkins Master and integrated JFrog artifactory with Jenkins by installing Artifactory plugin in Jenkins Master.

9. Created a Docker Image out of the jar file and committed that Docker Image into the Docker repository of the JFrog artifactory with the help of Docker Pipeline plugin. Added the Docker Build and Publish stage in Jenkinsfile.

10. EKS:

    1. Provisioned the EKS cluster with Terraform.
    2. Installed kubectl in Jenkins Slave.
    3. Installed AWS CLI v2 in Jenkins Slave to connect with AWS account.
    4. Downloaded Kubernetes credentials and cluster configuration from the cluster using the command
    5. aws eks update-kubeconfig --region <region_name> --name <cluster_name>

11. Pulled the Docker Image from the JFrog artifactory using Kubernetes secret and deployed it in our EKS cluster using deployment resource and exposed it to access from outside using service resource under a particular namespace. Added the deployment stage in Jenkinsfile.

12. Added the Prometheus helm chart repository and implemented the cluster monitoring using Prometheus and Grafana.

    • Note: Changed the default service type of Prometheus and Grafana services from ClusterIP to LoadBalancer to access them from the browser.

---

Hit the Star! ⭐

If you are planning to use this repo for learning, please hit the star. Thanks!

Author by DevCloud Ninjas

External image reference Source image

Source Files On GitHub

Use the guide first.

The full learning flow stays on this page. Open GitHub only when a step asks you to inspect code, fork the lab, or download source assets.

Read safety guide Open project source