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

2 min readJun 5, 2020

I hope you had visited the previous stories and this is the continuation of it.

Scenario:

This Lab Setup describes about the inclusion of Ansible to trigger the Playbooks in ’N’ number of target machines. The target machines can be assumed to be INT, QA, UAT, Production Environment.

I have divided the story in to Two Sections.

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

2.2 Pipeline CI/CD — GitHub, Maven, Jenkins, Artifactory, SonarQube, Docker, Ansible, 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
Ansible — Configuration Management Tool
Tomcat — Application Server

Pre-requisites:

Tools like Jenkins, Artifactory, SonarQube, Ansible 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, Ansible, Email Extension Plugin.