Part 3: Tools Integration with Jenkins

Install plugins, tools, and configuration

UpdatedMarch 4, 2026

Cloud & Infrastructure Engineer with 16+ years of experience in Azure, AWS & Hybrid IT environments. Passionate about DevOps, Automation, Terraform, CI/CD, and Enterprise Cloud Architecture. Building scalable, secure, and cost-optimized platforms. Based in Singapore 🇸🇬 | Sharing real-world hands-on cloud learnings.

Comments

Join the discussion

No comments yet. Be the first to comment.

DevSecOps Pipeline on AWS

Part 3 of 6

A step‑by‑step guide to building a secure, automated CI/CD pipeline on AWS using Jenkins, GitHub, Argo CD, Kubernetes, Prometheus, and Grafana. This series covers everything from code quality checks and vulnerability scanning to GitOps deployments and monitoring dashboards.

Up next

Part 4: Create CI CD Jobs in Jenkins

Pipeline building

More from this blog

Designing an AI-Powered Smart Building Architecture on Azure

Azure Solution for SmartBuildings

May 5, 20264 min read32

Designing an AI-Powered Smart Building Architecture on Azure

10 RAG Architectures You Should Know in 2026

RAG

May 3, 20265 min read42

10 RAG Architectures You Should Know in 2026

Part 10: Environment Variables in Pipelines

Make it variables and reusable

Mar 18, 20263 min read24

Part 10: Environment Variables in Pipelines

Part 9: Parameterized Pipelines

Scaling pipeline to accept Dynamic inputs

Mar 18, 20263 min read11

Part 8: Multibranch Pipelines

Scaling with branches

Mar 11, 20263 min read15

ask-abhi

22 posts

Go to Jenkins Master and click on Manage Jenkins --> Plugins --> Available plugins. Install the following plugins:
Install (Some of them get installed during the suggested plugins installation stage at start)

• OWASP (Dependency Check)
• SonarQube Scanner (Quality)
• Git (Code)
• Docker (Containerrization)
• Docker Pipeline
• Pipeline: Stage View
• Pipeline: Job
• Blue Ocean

Fork GitHub Repo: fullstack and share-library

Configure OWASP, move to Manage Jenkins --> Plugins --> Available plugins
After the OWASP plugin is installed, move to Manage Jenkins --> Tools

Log in to the SonarQube server and create the credentials for Jenkins to integrate with SonarQube
Navigate to Administration --> Security --> Users --> Token

Now, go to Manage Jenkins --> credentials
SonarQube: Integration
GitHub: Pull shared library and application source code
Docker Hub: to push the image
Create an API credentials for OWASP

GitHub user name and PAT (as a password)

Create and use an NVD API Key so OWASP can download with the API
Generate API Key. Go to: https://nvd.nist.gov/developers/request-an-api-key
Takes ~10 seconds. Key arrives by email.
Add Key to Jenkins Credentials In Jenkins: Manage Jenkins → Credentials → Global → Add Credentials
Type: Secret Text
ID: NVD_API_KEY
Secret: Fix Your API Key: 397ff9xxxxxxxxxxxxxx7b7d1c37

Go to Manage Jenkins --> Tools and search for SonarQube Scanner installations:

Now again, go to Manage Jenkins --> System and search for Global Trusted Pipeline Libraries:

Note: Before putting this shared library, Fork GitHub shared repository, and put the project repository URL of your repository.

Log in to the SonarQube server, go to Administration --> Webhook, and click on create

Public Ip is of Jenkins CI (Master node) and port 8080 because SonarQube is running on it only.

http://public-ip-of-master:8080/sonarqube-webhook

Now, go to the fullstack GitHub repository (hope you forked already) and under the Automations directory, update the instance-id field on both the updatefrontendnew.sh updatebackendnew.sh with the EKS worker's node instance id

Next...

💡

Part 4: Create CI CD Jobs in Jenkins

Command Palette

Comments

DevSecOps Pipeline on AWS

Part 4: Create CI CD Jobs in Jenkins

More from this blog