Automated Builds

CruiseControl

Main.ZipTie uses CruiseControl to manage the automated build.

• Cruisecontrol is setup to run after every checkin with a short idle time.
• A cvs checkout is performed against the 'ziptie' module alias.
• an ant ci_build is invoked against /Build/build.xml with no additional arguments.
• This build.xml file is in cvs with its default properties set to work with the automated build box.
• Every build is given a unique id based on the timestamp of the form YYYYMMDDhhmmss. This id is the version qualifier given to the build.
• Each build results in the a zip and a tar for each supported platform and a tar for an eclipse update site. These are placed in the cruisecontrol artifacts directory for the build.

Nightly Builds

All builds are created equal.

• Every night at midnight the last successful continuous build is copied from the cruisecontrol artifacts directory onto the www site for download. The 'latest' directory is a symbolic link which is updated to point at the directory containing the most recent nightly packages.
• If there has been no builds (read 'no checkins') since the last nightly build, no new build is copied.

Milestones

Milestones and Releases are manually picked from one these builds.