Use Continuous Integration
25 / 46 •
Coding •
This practice was ranked as advanced.
Click to read more. • This practice helps to increase
the team's agility.
Click to read more. • This practice helps to increase
the software quality.
Click to read more.
Click to read more. • This practice helps to increase
the team's agility.
Click to read more. • This practice helps to increase
the software quality.
Click to read more.
Intent
Catch any code integration problems as early as possible.
Motivation
Code changes and additions may introduce problems into the software system as a whole. This can be detected by running an automated build script each time that code is committed to the versioning repository.
Description
By running an automated build script at each commit, you achieve Continuous Integration (CI).
For this, you need to activate and configure a CI server in your development environment. Examples of CI servers include: TravisCI, CircleCI, and Appveyer. Some collaborative development environments include a built-in CI server.
To test not only possible compilation errors that may be introduced by code changes, but also possible runtime defects and code quality problems, the CI server must be configured to trigger one or more static analysis tools and your automated regression tests.
Adoption
Related
- Use Static Analysis to Check Code Quality
- Test all Feature Extraction Code
- Run Automated Regression Tests
Read more
25 / 46 •
Coding •
This practice was ranked as advanced.
Click to read more. • This practice helps to increase
the team's agility.
Click to read more. • This practice helps to increase
the software quality.
Click to read more.
Click to read more. • This practice helps to increase
the team's agility.
Click to read more. • This practice helps to increase
the software quality.
Click to read more.