NetworkAuthority Inventory uses CruiseControl for automating the build process, including building the Windows and Ubuntu installers. CruiseControl is set to watch CVS activity on cvs.ziptie.org and build when there is a relavent checkin. To view the current status of the build go to http://build.ziptie.org/.
| Build Server | www1.ziptie.org |
| CruiseControl home | /home/build/current-cc |
CruiseControl runs as a daemon process. See the CruiseControl website for information on configuring build projects, starting and stopping the daemon, etc.
The ziptie build project in CruiseControl is what watches the CVS head, and builds the entire NetworkAuthority Inventory product.
All other 'b' build projects are branch builds, building from the specified branch, but also building the NetworkAuthority Inventory or ZipTie product from that branch.
There are several build projects that start with forge. These projects are simply building adapter crates to be placed in a downloadable place for users of the Forge.
The root user on the www1.ziptie.org server has several cron jobs.
1 0 * * * /home/build/ziptie/pullnightly.pl 2 0 * * * /home/build/ziptie/pullnightly.pl b2007_09b 3 0 * * * /home/build/ziptie/pullnightly.pl b2008_04 4 0 * * * /home/build/ziptie/pullnightly.pl b2008_10 31 0 * * * /home/build/ziptie/pullnightlyforge.pl 32 0 * * * /home/build/ziptie/pullnightlyforge.pl forge_2008_04 33 0 * * * /home/build/ziptie/pullnightlyforge.pl forge_2008_10 0 1 * * * /home/build/ziptie/purge-artifacts.sh > /dev/null 2>&1
The pullnightly.pl script copies artifacts from the CruiseControl directory to the dev virtual web server on the same box for download.
The pullnightlyforge.pl script copies artifacts from the forge projects in CruiseControl over to the dev virtual web server's forge directory. This is the directory that the Forge looks at when constructing its web pages to see what versions of a plugin are available.