Continuous Integration

Internal

• CI/CD

Overview

Continuous Integration(CI) is an agile software development practice that involves the following:

• Verification of the build integrity by checking if the source code can be pulled from repository and built for deployment. The build process may include compilation, packaging and configuration.
• Running and validation of the unit tests: executes all unit tests created by developers and validates the test results. This step insures that the source code was not broken as a side effect of the commit.
• Running and validation of the integration tests.
• Identification of problems and alerting the teams.

In the DevOps culture, CI is mandatory, and it performed automatically by a tool that runs automation scripts to eliminate all human intervention during the CI process.

The CI process requires a source code repository and a continuous integration server, that pulls code from the source repository and runs the build. Developers must check in as often as possible, every time a new piece of functionality that is verified by unit tests that pass is added. The build must be completely automated and must run without human intervention, and it must be fast.

Testing - especially the integration testing - must be done in an environment that is as close to production as possible.

The CI process provides rapid feedback on the state of the project, each unit test or integration test-verified assertion that gets broken by a commit is immediately shared with the entire development team. The process is run every time there's a commit, presumably many times a day. Every member of the team must be able to easily access the build results.

The build process should generate software that can be deployed at any time - a good release candidate.

Jenkins is a Continuous Integration engine that can be adapted to drive Continuous Delivery too.

SonarQube is a static code analysis tool.

TO PROCESS:

• https://martinfowler.com/articles/continuousIntegration.html