1.1 Pipeline CI/CD — GitHub, Maven, Jenkins, Artifactory, SonarQube, Docker, Tomcat

• I have divided the story in to Two Sections.

1.1 Pipeline CI/CD — GitHub, Maven, Jenkins, Artifactory, SonarQube, Docker, Tomcat

1.2 Pipeline CI/CD — GitHub, Maven, Jenkins, Artifactory, SonarQube, Docker, Tomcat

In this article, we will discuss the Jenkins Declarative Pipeline Approach of Building the CI/CD Pipeline

Application: Spring Boot Hello World

Tools Used:

• GitHub — Source Code Management
• Maven — Build Tool
• Jenkins — Continuous Integration (CI/CD)
• Artifactory — Artifact Repository Manager
• SonarQube — Code Quality and Code Analysis
• Docker— Container Engine
• Tomcat — Application Server

Architecture

Pre-requisites:

• Tools like Jenkins, Artifactory, SonarQube Server is installed and the server is up and running
• Jenkins CI/CD — JFrog Artifactory Jenkins Integration
• Jenkins CI/CD — SonarQube Jenkins Integration
• Please make sure the following Jenkins Plugins are installed for this lab setup in the Jenkins Server ---- Pipeline, Artifactory, SonarQube Scanner for Jenkins, Email Extension Plugin.

Lab Setup:

• Creation of the Jenkins Job --- Pipeline Project

• Go to Pipeline Section, Select the Git Repository and save the job

GitHub URL: https://github.com/Dileeprithvi/DeclarativeCI-CD.git

Branch: working-1

• Clicking on the build to trigger the Job.
• Please find the Output Below.

Jenkins Console Output Log is attached for your reference in the GitHub.

To check the code is deployed correctly, Please follow the below URL Pattern:

http://<publicip>:8050/helloworld-0.0.1-SNAPSHOT/hello

• Jenkins Pipeline Stages Screenshot:

Pipeline Stages Screenshot

• Breaking the Code:

We can examine the Jenkinsfile in this Page.