Opus and UrbanSim Releases and Unit Tests

We use a subversion repository to manage our source code, and the CruiseControl continuous build process framework to manage the build process. Our code has an extensive collection of unit tests. Whenever someone checks a new version of a package into the subversion repository, CruiseControl runs all of the unit tests for that package and for any dependent packages. Depending on the package, there may be other actions as well -- for example, for the manual and tutorials, CruiseControl runs the latex document formatting program and the latex2html converter, and releases the resulting pdf and html files to the project website.

The following CruiseControl links give the status of building each project, as well as access to artifacts resulting from the build.

• CruiseControl (main page)
• CruiseControl dashboard

In addition, in our lab we have several traffic lights (real ones), which are controlled by the build system. When the light is green, all projects have passed all tests, and all is well. When the light is yellow, a project is currently being tested. But when the light is red, one or more unit tests have failed -- giving a very visible signal to our researchers that there is a problem that needs to be fixed. The build status page provides a virtual traffic light, mirroring the state of the real one.

So, before downloading the latest release from the subversion repository, you may want to check the the build status to make sure the light is green -- if it's red, wait until the problem is fixed, or get a stable release in the meantime.