Code Library

Understanding
That Continuous Integration itself is a software development Best Practice – central source file location, fully automated build, test and partly-automated distribution process that allows teams to build and test their software many times a day.

Buy In
This process starts with buy in for CI with Executives, which leads to Development Manager’s understanding; the end result being CI execution from Developers.

Continued Learning
Development Managers and Developers commit to learning and following the CI practices that best fit their environment.

Back Up
Environment and Source File back-up and recovery procedures are properly followed.

Quick Deployment
One of the main goals with CI is the speedy development from concept to user; ensure that frequent builds are consistently helping this process from start to finish.

No Broken Builds
The developer’s top priority is fixing breaks as new builds are created. Since CI involves a high amount of accountability, broken builds potentially affect every team member as well as the entire process. Team members must be able to rapidly trouble shoot and roll back changes to a successful build if needed.

Tight Build Promotion Process
Build promotion is how changes are taken from concept to development to the end user. The more consistent this process is, the more quickly ideas become a reality.