3 years ago

Category: Software, Database, Kubernetes, Ubuntu, github, automation, shell

This a series in which we’ll discuss the actual ci/cd pipeline along with the other concepts which can be invoked in the process of continuous integration and continuous deployment like SonarQube which is a code quality testing tool. Before Going to the example let us know the basic concepts like DevOps, ci/cd , need of ci/cd in real time and the architectural flow of ci/cd.

We are done with setup of Jenkins and Docker.

In this stage we are guiding the Jenkins to build an image with a version number , here “BUILD_NUMBER” of Jenkins will be used as a version number for the generated image and “registry” is the name of the docker image.

Setting the web hooks with ngrok: Wrapping up, we have installed the prerequisites, started Jenkins, installed required plugins for ci/cd, added the local paths of Git, shell, maven, Docker, Sonarqube and kubernetes to Jenkins, tested whether all are working fine in Jenkins environment with a sample Helloworld project, Created a pipeline project, Wrote a Jenkinsfile which will build and test the project, scan the project for code quality, generate a docker image based on the SonarQube quality gate, pushed the generated docker image onto docker hub, added ngrok generated forwarding address to webhooks of the repo and finally started our project ci/cd project onCommit of code.