In this project, I created an end-to-end Production like CI-CD pipeline while keeping in mind Securities Best Practices,DevSecOps principles and used all these tools Git, GitHub, Jenkins, Maven, JUnit, SonarQube, Jfrog Artifactory, Docker, Trivy, AWS S3, Docker Hub, GitHub CLI, EKS, ArgoCD, Prometheus, Grafana, Slack and Hashicorp Vault, to achieve the goal.

1. When an event (commit) will occur in the application code GitHub repo, the GitHub webhook will push the code to Jenkins and Jenkins will start the build.

2. Maven will build the code, if the build fails, the whole pipeline will become a failure and Jenkins will notify the user using Slack, If build success then

3. Junit will do unit testing, if the application passes test cases then will go to the next step otherwise the whole pipeline will become a failure Jenkins will notify the user that your build fails.

4. SonarQube scanner will scan the code and will send the report to the SonarQube server, where the report will go through the quality gate and gives the output to the web Dashboard.

5. In the quality gate, we define conditions or rules like how many bugs or vulnerabilities, or code smells should be present in the code. Also, we have to create a webhook to send the status of quality gate status to Jenkins. If the quality gate status becomes a failure, the whole pipeline will become a failure then Jenkins will notify the user that your build fails.

6. After the quality gate passes, Artifacts will be sent to Jfrog Artifactory. If artifacts send to the artifactory successfully then will go to the next stage otherwise the whole pipeline will become a failure Jenkins will notify the user that your build fails.

7. After successful artifacts push to Artifactory, Docker will build the docker image. if the docker build fails when the whole pipeline will become a failure and Jenkins will notify the user that your build fails.

8. Trivy will scan the docker image, if it finds any Vulnerability then the whole pipeline will become a failure, and the generated report will be sent to s3 for future review and Jenkins will notify the user that your build fails.

9. After the Trivy scan docker images will be pushed to the docker hub, if the docker fails to push docker images to the docker hub then the pipeline will become a failure and Jenkins will notify the user that your build fails.

10. After the docker push, Jenkins will clone the Kubernetes manifest repo from the feature branch, if the repo is already present then it will only pull the changes. If Jenkins is unable to clone the repo then the whole pipeline will become a failure and Jenkins will notify the user that your build fails.

11. After Cloning the repo, Jenkins will update the image tag in the deployment manifest. If Jenkins is unable to update the image tag then the whole pipeline will become a failure and Jenkins will notify the user that your build fails.

12. After updating the image tag, Jenkins will commit the change and push the code to the feature branch. If Jenkins is unable to push the changes to the feature branch then the whole pipeline will become a failure and Jenkins will notify the user that your build fails.

13. After pushing changes to the feature branch, Jenkins will create a pull request against the main branch. If Jenkins is unable to create a pull request then the whole pipeline will become a failure and Jenkins will notify the user that your build fails.

14. After the pull request creation, a senior person from the team will review and merge the pull request.

15. After merging the feature branch into the main branch, ArgoCD will pull the changes and deploy the application into Kubernetes.

1. JDK
2. Git
3. Github
4. GitHub CLI
5. Jenkins
6. Sonarqube
7. Jfrog Artifactory
8. Docker
9. Trivy
10. AWS account
11. AWS CLI
12. Docker Hub account
13. Terraform
14. EKS Cluster
15. kubectl
16. ArgoCD
17. Helm
18. Prometheus & Grafana
19. Hashicorp Vault
20. Slack

1. 2 t2.medium ( ubuntu) EC2 Instances – 1. one for sonarqube and Hashicorp vault server 2. another for Jfrog Artifactory

2. 1 t2.large (ubuntu ) EC2 Instance - For Jenkins, Docker, Trivy, AWS CLI, Github CLI, Terraform

3. EKS Cluster with t3.medium nodes

Push all the web application code files into GitHub

1. Installation guide is available here https://github.com/praveensirvi1212/DevSecOps-project/blob/main/Jenkins_installation.md
2. After installation, install the suggested plugins
3. Open Jenkins Dashboard and install required plugins – SonarQube Scanner, Quality gates, Artifactory, Hashicorp Vault, Slack, Open Blue Ocean
4. go to manage Jenkins > manage plugins > search for plugins > Download now and install after restart

1. Install docker using this command

sudo apt install docker.io

2. add the current user and Jenkins user into the docker group

sudo usermod -aG docker $USER
sudo usermod -aG docker jenkins

1. Insatll trivy using these commands

sudo apt-get install wget apt-transport-https gnupg lsb-release
wget -qO - https://aquasecurity.github.io/trivy-repo/deb/public.key | sudo apt-key add -
echo deb https://aquasecurity.github.io/trivy-repo/deb $(lsb_release -sc) main | sudo tee -a /etc/apt/sources.list.d/trivy.list
sudo apt-get update
sudo apt-get install trivy

1. install aws cli using these commands

sudo apt install unzip
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install

1. install GitHub cli using these commands

type -p curl >/dev/null || (sudo apt update && sudo apt install curl -y)
curl -fsSL https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo dd of=/usr/share/keyrings/githubcli-archive-keyring.gpg \
&& sudo chmod go+r /usr/share/keyrings/githubcli-archive-keyring.gpg \
&& echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.list > /dev/null \
&& sudo apt update \
&& sudo apt install gh -y

1. install terraform using these commands

sudo apt-get update && sudo apt-get install -y gnupg software-properties-common
wget -O- https://apt.releases.hashicorp.com/gpg | \
gpg --dearmor | \
sudo tee /usr/share/keyrings/hashicorp-archive-keyring.gpg
gpg --no-default-keyring \
	--keyring /usr/share/keyrings/hashicorp-archive-keyring.gpg \
	--fingerprint
echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] \
https://apt.releases.hashicorp.com $(lsb_release -cs) main" | \
sudo tee /etc/apt/sources.list.d/hashicorp.list
sudo apt update
sudo apt-get install terraform

1. install docker on the sonarqube server

sudo apt update
sudo apt install docker.io

2. create a docker container to install SonarQube

sudo docker run -d -p 9000:9000 --name sonarqube sonarqube  

HashiCorp Vault is a secret-management tool specifically designed to control access to sensitive credentials in a low-trust environment.

1. Installation vault using these commands

sudo curl -fsSL https://apt.releases.hashicorp.com/gpg | sudo apt-key add -
sudo apt-add-repository "deb [arch=amd64] https://apt.releases.hashicorp.com $(lsb_release -cs) main"
sudo apt update
sudo apt install vault -y

1. install the docker

sudo apt update
sudo apt install docker.io

2. install Jfrog Artifactory

sudo docker pull docker.bintray.io/jfrog/artifactory-oss:latest
sudo mkdir -p /jfrog/artifactory
sudo chown -R 1030 /jfrog/
sudo docker run --name artifactory -d -p 8081:8081 -p 8082:8082 \
	-v /jfrog/artifactory:/var/opt/jfrog/artifactory \
	docker.bintray.io/jfrog/artifactory-oss:latest

Slack is a workplace communication tool, “a single place for messaging, tools and files.” .

Install Slack from the official website of Slack https://slack.com/intl/en-in/downloads/linux

To create EKS Cluster using Terraform, I have put the Terraform code here - https://github.com/praveensirvi1212/medicure-project/tree/master/eks_module

Suggestion – create eks cluster after successful configuration of jenkins server. When jenkins is able to create pull request in the manifest repo.

Run this command after eks cluster creation to update or configure .kube/config file

aws eks --region your-region-name update-kubeconfig --name cluster-name

I am assuming that you have already Kubernetes cluster running

1. use these commands to install argocd

kubectl create namespace argocd 
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

2. edit the argocd-server service to NodePort to access argocd ui

kubectl -n argocd edit svc argocd-server

1. use these commands to install the helm

curl https://baltocdn.com/helm/signing.asc | gpg --dearmor | sudo tee /usr/share/keyrings/helm.gpg > /dev/null
sudo apt-get install apt-transport-https --yes
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/helm.gpg] https://baltocdn.com/helm/stable/debian/ all main" | sudo tee /etc/apt/sources.list.d/helm-stable-debian.list
sudo apt-get update
sudo apt-get install helm

1. use helm to install Prometheus and grafana

helm repo add stable https://charts.helm.sh/stable
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm search repo prometheus-community
kubectl create namespace prometheus
helm install stable prometheus-community/kube-prometheus-stack -n prometheus
kubectl get pods -n prometheus
kubectl get svc -n prometheus
#in order to make Prometheus and grafana available outside the cluster, use LoadBalancer or NodePort instead of ClusterIP.
#Edit Prometheus Service
kubectl edit svc stable-kube-prometheus-sta-prometheus -n prometheus
#Edit Grafana Service
kubectl edit svc stable-grafana -n prometheus
kubectl get svc -n prometheus

#Access Grafana UI in the browser using load balancer or nodeport

UserName: admin 
Password: prom-operator

1. go to Manage Jenkins > configure tools > go to maven> give some name and click on install automatically
2. go to Manage Jenkins > configure tools > go to sonarqube scanner > give some name and click on install automatically

I am assuming that your Vault server is installed and running

• open the /etc/vault.d/vault.hcl file with vi or nano
• replace all the content of this file with this

storage "raft" {
  path    = "/opt/vault/data"
  node_id = "raft_node_1"
}

listener "tcp" {
  address     = "0.0.0.0:8200"
  tls_disable = 1
}

api_addr = "http://127.0.0.1:8200"
cluster_addr = "https://127.0.0.1:8201"
ui = true

sudo systemctl stop vault
sudo systemctl start vault

export VAULT_ADDR='http://127.0.0.1:8200'

vault operator init

• copy the unseal tokens and initial root token, save it somewhere for later use

vault operator unseal

• Paste the first unseal token here

vault operator unseal

• Paste the second unseal token here

vault operator unseal

• Paste the third unseal token here

vault login <Initial_Root_Token>

• <Initial_Root_Token> is found in the output of vault operator init

vault auth enable approle

vault write auth/approle/role/jenkins-role token_num_uses=0 secret_id_num_uses=0 policies="jenkins"

• This app role will use for jenkins integration

vault read auth/approle/role/jenkins-role/role-id

• Copy the role_id and token, and store somewhere

vault write -f auth/approle/role/jenkins-role/secret-id

• Copy the secret-id and token, store them somewhere

1. Access the sonarqube ui using the public IP of the server and port 9000
2. default username-password admin and admin

1. chose use global setting
2. create a project manually, give some name to project, project key
3. click on setup
4. click on other ci
5. give some name to the token and click on generate, save it for a later user
6. click on global
7. select the project type, in this case, I used Maven
8. copy the whole command and save it somewhere

1. Click on Quality Gates
2. create a new Quality Gate according to your conditions
3. click on Projects > click on all > select your project
4. set as default

1. click on Administration
2. click on Configuration > click on webhooks
3. create a webhook > Give some name
4. for url use http://jenkins-server-url-with-port/sonarqube-webhook/
5. in secret leave the blank
6. click on create

1. access the UI with public IP and port 8081
2. use username-password as admin and password
3. update the password
4. create a Maven repo
5. now go to Administration > User management > Create a new user
6. now go to Repositories > create > locally > give some name like my-local-repo

1. login into aws account
2. search for S3
3. create a bucket with a unique name

If you already have a dockerhub account then no need to create another

1. go to dockerhub official website
2. click on sign up
3. fill in the details and sing up
4. login into dockerhub

Note: we can create token from dockerhub to integrate jenkins but in this case, I am using docker username and password.

1. go to this site https://slack.com/intl/en-in
2. sign up with Google
3. create a workspace
4. just give a name
5. you can skip add team member
6. give some name to team working ( channel name like - cicd-pipeline)
7. now go to this site https://slack-t8s2905.slack.com/intl/en-in/apps
8. login into your workspace (if need)
9. now click on Get Essential Apps
10. search Jenkins in search bar > click on it
11. click on Add to Slack
12. select channel name
13. click on Add Jenkins CI Integration
14. go down to step 3 and copy Integration Token Credential ID and save it somewhere
15. click on Save settings

1. Go to this site https://api.slack.com/apps
2. click on Create New App
3. select From scratch
4. give some app name
5. pick your workspace
6. click on Create App
7. go to OAuth & Permission
8. go to Scope > Bot Token Scope
9. search in the search bar and select chat:write ,chat:write.customize
10. now to up to OAuth Token for Your Workspace
11. click on Install to workspace
12. allow your app to access your workspace
13. now copy Bot user OAuth Token and save it somewhere
14. now open slack , you will find your app in Apps
15. now create a channel - click on channels > create channel > give some name to channel > create
16. now in message bar type @your-app-name and click on send icon > click on add to channel

run all these commands into the vault server

1. enable secrets path

vault secrets enable -path=secrets kv

2. write the secret into secret path

vault write secrets/creds/docker username=abcd password=xyz

likewise, we can store all the credentials in the vault server. I have stored only the docker credential but you can store all your credential like this.

3. create a jenkins policy file with vi or nano jenkins-policy.hcl

path "secrets/creds/*" {
 capabilities = ["read"]
}

the policy is created with * means the vault server can read credentials from every path. No need to create policies for each path like secrets/creds/docker , secrets/creds/slack etc…

4. run this command to create a policy

vault policy write jenkins jenkins-policy.hcl

1. go to Jenkins> Manage Jenkins >Manage Credentials > system > Add credentials > Vault App Role Credentials > Paste role-id and secret-id token (we create in Vault - approle) and save and apply.
2. now to Manage Jenkins > configure system/system> search for vault plugin
3. give the URL of the vault server
4. attach the credentials we created
5. click on Advanced
6. select k/v engine as 1
7. click on skip ssl verification
8. Apply and Save

1. go to Manage Jenkins>Manage Credentials > system > Add credentials > secret text file > paste the token we create in sonarqube and save and apply.
2. now to Manage Jenkins > configure system/system> search for SonarQube Server
3. enable the environment variables
4. write the name of Sonaqube server
5. paste the url of SonarQube server
6. select the credential
7. Apply and Save

1. go to Manage Jenkins>Manage Credentials > system > Add credentials > username and password > write the username and password we created in jforg artifacotry and save and apply.
2. now to Manage Jenkins > configure system/system> search for Jfrog
3. give instance id as artifactory name
4. Jfrog Platform url - artifactory url like - http://localhost:8082
5. click on Advanced
6. JFrog Artifactory URL - http://localhost:8082/artifactory
7. JFrog Distribution URL - http://localhost:8082/distribution
8. Default Deployer Credentials – give username and password of artifactory (not admin user)
9. Apply and save

1. for S3 integration we will configure aws cli in the pipeline itself
2. create credentials for aws cli, use both as the secret text

1. go to Manage jenkins >Manage Credentials > system > Add credentials > vault Username-Password Credential
2. namespace – leave blank
3. Prefix Path – leave blank
4. Path – secrets/creds/docker
5. Username Key- username
6. Password key – password
7. k/v engine – 1
8. id – give some id like docker-cred
9. Description - give some description
10. click on Test Vault Secrets retrieval > should give output as secrets retrieved successfully otherwise reconfigure the vault server in jenkins
11. Apply and Save

1. go to Manage Jenkins>Manage Credentials > system > Add credentials > secret text file > give some name to credentials, paste the token we create in the Slack app and save and apply.
2. now to Manage Jenkins > configure system/system> search for Slack
3. workspace – your workspace name ( you create after login into Slack)
4. Credential – attach the slack token
5. Default channel name – write the channel name we created at the time of slack installation like - #cicd-pipeline
6. Apply and save

1. go to GitHub > go to application code repo > settings
2. go to webhook > Add webhook
3. Payload URL - http://jenkins-server-public-ip-with-port/github-webhook/
4. click on Add Webhook

1. access the argocd UI – node public ip and node port
2. user username as admin
3. for password run this command

 kubectl -n argocd get secret argocd-initial-admin-secret -o yaml

4. copy the password and decode it using

echo “copied-password” | base64 -d

5. copy the decoded password and login into argocd
6. go to User Info – update password
7. now go to Application
8. click on New Application
9. give app name
10. chose Project Name as default
11. SYNC Policy – Automatic
12. enable PRUNE RESOURCES and SELF HEAL
13. SOURCE-
14. Repository URL – give your repo URL where you stored the k8s manifest
15. Path – yamls
16. DESTINATION -
17. Cluster Url – chose default
18. namespace- default
19. click on create

1. encode your Slack token using this command ( Bot Token )

echo "your-slack-token" | base64

2. edit argocd-notifications-secret secret to add slack token

kubectl -n argocd edit secret argocd-notifications-secret

3. add data field after apiVersion: v1, Replace xxxx-xxxxx-xx with your encoded slack token

data:
  slack-token: xxxxx-xxxxxx-xxxxxx

4. now edit argocd-notifications-cm configmap

kubectl -n argocd edit cm argocd-notifications-cm

5. add this service for slack after apiVersion: v1

data:
  service.slack: |
    token: $slack-token
    username: argocd-bot
    icon: ":rocket:"
  template.app-sync-succeeded-slack: "message: | \n      Application {{.app.metadata.name}}
    is now {{.app.status.sync.status}}\n"
  trigger.on-sync-succeeded: |
    - when: app.status.sync.status == 'Synced'
      send: [app-sync-succeeded-slack]

6. add slack notification annotation in application

kubectl -n argocd edit application your-app-name-you-created-in-argocd

7. add this annotation in metadata section like this

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  annotations:
    notifications.argoproj.io/subscribe.on-sync-succeeded.slack: your-slack-channel-name
  name: argocd-demo
  namespace: argocd

use this docs to import grafana Dashboard into grafana https://www.coachdevops.com/2022/05/how-to-setup-monitoring-on-kubernetes.html

pipeline {
    agent any
    tools {
        maven 'apache-maven-3.0.1' 
    }
    stages {
        stage('Example') {
            steps {
                sh 'mvn --version'
            }
        }
    }
}

1. Define a stage as git checkout
2. go to this site https://opensource.triology.de/jenkins/pipeline-syntax/
3. search for checkout: check out version control
4. give your GitHub URL, branch and generate the pipeline syntax
5. paste it into stage steps git check

stage('Checkout git') {
            steps {
              git branch: 'main', url:'https://github.com/praveensirvi1212/DevOps_MasterPiece-CI-with-Jenkins.git'
            }
        }

1. Define a stage as Build and Junit test
2. go to this site https://opensource.triology.de/jenkins/pipeline-syntax/
3. search for sh: shell script
4. give your shell command and generate the pipeline syntax
5. paste it into stage > steps > sh ‘ shell command’

stage ('Build & JUnit Test') {
	steps {
		sh 'mvn install' 
	}
	
}

In this stage, I used withSonarQubeEnv to Prepare the SonarQube Scanner environment and shell command sh

1. Define a stage SonarQube Analysis
2. paste the command that we created at the time of the sonarqube project creation

stage('SonarQube Analysis'){
            steps{
                withSonarQubeEnv('SonarQube-server') {
                        sh '''mvn clean verify sonar:sonar \
                        -Dsonar.projectKey=gitops-with-argocd \
                        -Dsonar.projectName='gitops-with-argocd' \
                        -Dsonar.host.url=$sonarurl \
                        -Dsonar.login=$sonarlogin'''
                }
            }
        }

This step pauses Pipeline execution and waits for the previously submitted SonarQube analysis to be completed and returns quality gate status. Setting the parameter abortPipeline to true will abort the pipeline if the quality gate status is not green.

1. Define a stage as a Quality gate
2. go to this site https://opensource.triology.de/jenkins/pipeline-syntax/
3. search for waitForQualityGate: Wait for SonarQube analysis to be completed and return quality gate status
4. generate pipeline syntax and paste it into steps
5. timeout is optional

stage("Quality Gate") {
            steps {
              timeout(time: 1, unit: 'HOURS') {
                waitForQualityGate abortPipeline: true
              }
            }
          }

1. We wrap the steps in a script block to execute them as a Groovy script.
2. Inside the try block, we create a reference to the Artifactory server using the Artifactory.newServer method. You need to provide the URL of your Artifactory instance and the credentials ID configured in Jenkins.
3. We define an uploadSpec as a JSON string, specifying the pattern of files to upload and the target repository in Artifactory.
4. We call the server.upload(uploadSpec) method to upload the files to Artifactory based on the specified upload specification.
5. If any exception occurs during the upload process, the catch block will be executed, and an error message will be displayed.

steps {
                script {
                    try {
                        def server = Artifactory.newServer url: 'http://13.232.95.58:8082/artifactory', credentialsId: 'jfrog-cred'
                        def uploadSpec = """{
                            "files": [
                                {
                                    "pattern": "target/*.jar",
                                    "target": "${TARGET_REPO}/"
                                }
                            ]
                        }"""
                        
                        server.upload(uploadSpec)
                    } catch (Exception e) {
                        error("Failed to deploy artifacts to Artifactory: ${e.message}")
                    }
                }
            }
        }

First, write your dockerfile to build docker images. I have posted my dockerfile in the application repo code In this stage, I used the shell command sh to build the docker image

1. Define a stage Docker Build
2. go to this site https://opensource.triology.de/jenkins/pipeline-syntax/
3. search for sh: shell script
4. give your shell command to build image > generate pipeline syntax
5. I used the build-id of jenkins and git commit id for versions of docker images

sstage('Docker  Build') {
            steps {
               
      	         sh 'docker build -t ${IMAGE_REPO}/${NAME}:${VERSION}-${GIT_COMMIT} .'
                
            }
        }

In this stage, I trivy shell command sh to scan the docker image

1. Define a stage Trivy Image scan
2. go to this site https://opensource.triology.de/jenkins/pipeline-syntax/
3. search for sh: shell script
4. give your Trivy shell command to scan the docker image

stage('Image Scan') {
            steps {
      	        sh ' trivy image --format template --template "@/usr/local/share/trivy/templates/html.tpl" -o report.html 		${IMAGE_REPO}/${NAME}:${VERSION}-${GIT_COMMIT} '
            }
        }
	}
}

In this stage, I used the shell command sh to Upload Scan report to AWS S3

1. Define a stage Upload report to AWS S3
2. first create an AWS s3 bucket
3. go to this site https://opensource.triology.de/jenkins/pipeline-syntax/
4. search for sh: shell script
5. give your shell command to upload the object to aws s3

stage('Upload Scan report to AWS S3') {
              steps {
                  
                //  sh 'aws configure set aws_access_key_id "$AWS_ACCESS_KEY_ID"  && aws configure set aws_secret_access_key "$AWS_ACCESS_KEY_SECRET"  && aws configure set region ap-south-1  && aws configure set output "json"' 
                  sh 'aws s3 cp report.html s3://devops-mastepiece/'
              }
        }

In this stage, I used the shell command sh to push the docker image to the docker hub. I stored Credentials in Vault and accessed them in jenkins using the Vault key. You can store DockerHub credentials in jenkins and use them as environment variables

1. Define a stage Docker images push
2. go to this site https://opensource.triology.de/jenkins/pipeline-syntax/
3. search for sh: shell script
4. give your shell command to push docker images to the docker hub

stage ('Docker Build') {
           steps {
               withVault(configuration: [skipSslVerification: true, timeout: 60, vaultCredentialId: 'vault-token', vaultUrl: 'http://13.232.53.209:8200'], vaultSecrets: [[path: 'secrets/creds/docker', secretValues: [[vaultKey: 'username'], [vaultKey: 'password']]]]) {
                   
                   sh "docker login -u ${username} -p ${password} "
                   sh 'docker push ${IMAGE_REPO}/${NAME}:${VERSION}-${GIT_COMMIT}'
   	    	sh 'docker rmi  ${IMAGE_REPO}/${NAME}:${VERSION}-${GIT_COMMIT}'
                   
                   
               }
           }
       }

1. in this stage first we check whether the repo already exists or not
2. if exists then pull the changes
3. if not then will clone the repo

stage('Clone/Pull Repo') {
           steps {
               script {
                   if (fileExists('DevOps_MasterPiece-CD-with-argocd')) {

                       echo 'Cloned repo already exists - Pulling latest changes'

                       dir("DevOps_MasterPiece-CD-with-argocd") {
                         sh 'git pull'
                       }

                   } else {
                       echo 'Repo does not exists - Cloning the repo'
                       sh 'git clone -b feature https://github.com/praveensirvi1212/DevOps_MasterPiece-CD-with-argocd.git'
                   }
               }
           }
       }

1. used sed command to replace images tag in deployment manifests

stage('Update Manifest') {
            steps {
                dir("DevOps_MasterPiece-CD-with-argocd/yamls") {
                    sh 'sed -i "s#praveensirvi.*#${IMAGE_REPO}/${NAME}:${VERSION}-${GIT_COMMIT}#g" deployment.yaml'
                    sh 'cat deployment.yaml'
                }
            }
        }

1. set the global username
2. set the remote repo URL
3. checkout the branch to feature
4. stage the changes
5. commit the changes
6. push the changes to the feature branch

stage('Commit & Push') {
            steps {
                withCredentials([string(credentialsId: 'GITHUB_TOKEN', variable: 'GITHUB_TOKEN')]) {
                    dir("DevOps_MasterPiece-CD-with-argocd/yamls") {
                        sh "git config --global user.email '[email protected]'"
                        sh 'git remote set-url origin https://${GITHUB_TOKEN}@github.com/${GIT_USER_NAME}/${GIT_REPO_NAME}'
                        sh 'git checkout feature'
                        sh 'git add deployment.yaml'
                        sh "git commit -am 'Updated image version for Build- ${VERSION}-${GIT_COMMIT}'"
                        sh 'git push origin feature'
                    }
                }    
            }
        }

The reason to create a pull request is that argocd is sync automatically with Git Hub. GitHub is the only single source of truth for argocd. So if jenkins push the changes to the main branch then argocd will deploy changes directly without reviewing the changes. This should not happen in the Production environment. That’s why we create pull requests against the main branch. So a senior person from the team can review the changes and merge them into the main branch. Then n then only changes should go to the production environment.

Here token.txt contain the GitHub token, the reason for storing the GitHub token in the text file bcoz gh auth login --with-token accept only STDIN Input

stage('Raise PR') {
            steps {
                withCredentials([string(credentialsId: 'GITHUB_TOKEN', variable: 'GITHUB_TOKEN')]) {
                    dir("DevOps_MasterPiece-CD-with-argocd/yamls") {
                        sh '''
                            set +u
                            unset GITHUB_TOKEN
                            gh auth login --with-token < token.txt
                            
                        '''
                        sh 'git branch'
                        sh 'git checkout feature'
                        sh "gh pr create -t 'image tag updated' -b 'check and merge it'"
                    }
                }    
            }
        } 

In post build action I used Slack notification. After the build jenkins will send a notification message to Slack whether your build success or failure.

1. go to jenkins > your project > pipeline syntax > search for slacksend: send slack message
2. write your channel name and message > generate pipeline syntax.

post{
   always{
   	sendSlackNotifcation()
   }
}

sendSlackNotification function

def sendSlackNotifcation()
{
   if ( currentBuild.currentResult == "SUCCESS" ) {
       buildSummary = "Job_name: ${env.JOB_NAME}\n Build_id: ${env.BUILD_ID} \n Status: *SUCCESS*\n Build_url: ${BUILD_URL}\n Job_url: ${JOB_URL} \n"
       slackSend( channel: "#devops", token: 'slack-token', color: 'good', message: "${buildSummary}")
   }
   else {
       buildSummary = "Job_name: ${env.JOB_NAME}\n Build_id: ${env.BUILD_ID} \n Status: *FAILURE*\n Build_url: ${BUILD_URL}\n Job_url: ${JOB_URL}\n  \n "
       slackSend( channel: "#devops", token: 'slack-token', color : "danger", message: "${buildSummary}")
   }
}

https://github.com/praveensirvi1212/DevOps_MasterPiece-CI-with-Jenkins/blob/main/Jenkinsfile

Sorry, I forgot to change the stage name while building the job, but don't worry I made changes in the Jenkins file.

SonarQube Quality gate status is green and passed.
You can apply your custom quality gate like there should be zero ( bug, Vulnerability, code smell ) and if your code has greater than 0 (bugs, vulnerability, code smells). Then your quality gate status will become a failure or red. If your quality gate status becomes a failure, stages after the quality gate will be a failure.