Jul 9

Written by: Mike Benson
7/9/2008 3:19 PM

While this may not seem like a big deal, internally it is.  Every two hours a process kicks off that rebuilds all of our libraries, runs all the test cases and publishes the results to all of our developers.  What this does for us is make sure that no developer "breaks the build", or more practically, when it does happen it we know it as soon as possible and can mitigate damage early on.

This also means that our versioning system is in place, our build versions match the source code version and the defect tracking version.  So, what this all mean to you? The software is more stable, more reliable and defects are easier to repeat (and therefore fix). 

 

Tags: