Charm++ Automated build-and-test script
  Orion Sky Lawlor, olawlor@acm.org, 2003/2/21

INTRODUCTION

This is a small set of scripts that use scp and ssh 
to remotely build and test charm++.  The scripts are run 
every night to flush out bugs in Charm++, hence the 
name "autobuild".  They can also be run manually,
normally by the Charm++ developers.

CONFIGURATION FILES

system_list: Lists machines to build on.  Colon-separated format
  containing:
    charm++-version:user@host:ssh-version:build-dir:startup command

config: Lists status web page address and e-mail addresses.
   "sourced" by bourne shell scripts, so it's name=value.
   Only used if "autobuild.real" is present.


SCRIPTS

build: Actually does the scp, ssh, and remote build.

build_on_all: Call build_on_system for each version in system_list

autobuild: Nightly build driver script.  Checks a new copy 
  of charm out of CVS and calls the other scripts.

autobuild.cron: Calls autobuild in a cron-suitable way.

build_on_system: Actually does the scp, ssh, and remote build
  Specifically, calls	
  ssh <build machine> and runs:
	cd <build directory>
	tar xvf charm.tar
	cd charm
	./build AMPI <version> -O
	../instead_test.sh || ./build test <version> -O
	../post_test.sh

autobuild.real: This file, if present, indicates that we should
  copy the resulting build and binaries to the website.

system_list.test: For debugging your system_list file.

update_email: Send out status email.

update_web: Bring status web page up to date.

update_web_start: Begin a new status web page.

