Continuous Integration
Continuous Integration
You can develop good software regardless of the technology you are working on by following certain fundamental practices:
- Plan for code changes
- Perform the code changes, then compile and test
- Check the results
- Act on the results
Adapt Continuous Integration to help you with seamless software development.
What is Continuous Integration?
The earlier you detect defects, the cheaper they are to fix - David Farley
Continuous Integration (CI) is a software development practice, where developers will commit (integrate) their code changes to a shared repository frequently. Such commits must trigger automated builds and tests, enabling quick verification of the changes at an early stage of the development cycle, rather than waiting to detect bugs after the code is completely developed.
Why Continuous Integration?
Continuous Integration does not get rid of bugs, but it does make it easier to find and remove.
Source: Martin Fowler
When developers cultivate the habit of integrating their code changes regularly:
- Changes will be typically small
- Errors can be detected quickly
- Pointing out the change that introduced an error can be done quickly
How to Make a Process Continuous?
As a first step towards adopting Continuous Integration, identify and make a software development process continuous.
Continuous Integration - Services
Continuous Integration includes the following:
- Source Code Control
- Code Compile
- Integrate Database Changes
- Run Tests
- Code Inspection
Continuous Integration - Workflow
