Continuous Integration

A Continuous Integration(CI) pipeline is a series of steps that must be performed in order to deliver a new version of software. Continuous Integration is a software development method where members of the team can integrate their work at least once a day. In this method, every integration is checked by an automated build to search the error.

Stages of a CI Pipeline

• Check-in/Source Code
• Build and Unit Test
• SonarQube
• Integration Test

CI Pipeline Workflow

1. Check-in/Source Code

Check-in/Source Code - In the source stage, CI pipeline is triggered by a code repository. Any change in the program triggers a notification to the CI tool that runs an equivalent pipeline.

These are the All Workflows,

2. Build and Unit Test

Build - The stage where the application is compiled. This is the second stage of the CI/CD Pipeline in which you merge the source code and its dependencies. It is done mainly to build a runnable instance of software.

Build running steps -

CI Build And Analyze result

3. SonarQube Analysis

SonarQube is an Open Source tool for continuous inspection of code quality. SonarQube has a collection of rules to analyze source code at compile time to identify potential vulnerabilities, bugs, anti-patterns, refactoring and poor coding practices.

Sonar Scan running steps -

SonarScan Build and Analyze -

4. Integration Test

Integration Test - Test Stage includes the execution of integration tests to validate the correctness of code and the behaviour of the software. This stage prevents easily reproducible bugs from reaching the clients.

Integration Test running steps -

We have run ./gradlew test integrationTest jacocoTestReport command on console

Build Result -**