Compass Version1.2

Creating a Regularly Scheduled CVS Build Plan

This is the first part of a two part series on creating a CVS build plan.  For this series, we assume that we already have the following:

1. A Compass admin user called admin who is setting up the build plan
2. A Compass project called CVS Example Code that contains a project written with python.

The first step in setting up the build plan is to navigate to the build editor page, by first accessing the project details page of the CVS Example Code project and then clicking 'Create Build' button. 

This will ask us for the name of the project and the files we want to save with every execution of the build plan.  We will call our new build plan 'CVS Build Plan' and since we don't know if we want anything saved with each build yet, we will leave the 'Save File or Dir' box empty.  After hitting 'OK' we are taken to the build editor page which looks like this:

The first thing we need to do is to add a build step to check out our project from the CVS repository.  We click the 'Add Script' button and an empty build step is added to the build plan:

Now we fill in the Name, select 'CVS Argument Checkout' from the scripts drop down box.  The CVS Argument Checkout script requires us to put the cvs URL as build step argument so we add ':pserver: This e-mail address is being protected from spambots. You need JavaScript enabled to view it ' as the argument and now our build step looks like this:

The 'CVS Argument Checkout' script's usage notes also tell us that we need to put the module name that we want to check out in the default variable MODULE_NAME.  So we open up the defaults window and enter our module name there and that looks like this:

After clicking 'OK' we are done setting up the CVS checkout script.  Python does not require any compiling so we do not need a compilation build step but we do have a test suite written using PyUnit.  In the second part of this series we add a PyUnit execute build step.