This file is cipres/framework/etc/build_scripts/readme.txt. To set up a machine to do nightly builds: * Pick a directory in which to run the build. From now on I'll refer to this directory as /Users/Shared. * Copy the build scripts from the svn repository to /Users/Shared. svn checkout \ http://nladr-cvs.sdsc.edu/svn/CIPRES/cipresdev/trunk/cipres/framework/etc/build_scripts/ . * Copy the autoconf_helpers from the svn repository to /Users/Shared/autoconf_helpers: svn checkout \ http://nladr-cvs.sdsc.edu/svn/CIPRES/cipresdev/trunk/cipres/framework/etc/autoconf_helpers/ \ autoconf_helpers * Move nightlybuildrc to your home directory, Modify ~/nightlybuildrc - Set PATH such that svn, cvs and ant 1.6.5 will be found. - Set the buildMachine env variable for your machine - Change the webUserName if you do not have $USER set (or if your username on myfiles.sdsc.edu differs from your local username). * Create CIPRES_dev and BigCIPRES_dev in /Users/Shared. If you'll be building from any tags also create CIPRES_ and BigCIPRES_. These directories need to have archives of third party tools copied to them before the scripts are run. The scripts will add archives of our cipres code. The archives third_party_tools.tgz and more_tools.tgz are available from the snapshot web site. - Expand third_party_tools.tgz in each of these directories. - Also expand more_tools.tgz in the Big* directories. - The developer's release branch requires paup-4.11.tgz but the trunk uses paup-4.0b11.tgz. You can remove the version that's unneeded in each of the directories. * Make sure passwordless authentication is configured for FSU cvs and for myfiles.sdsc.edu. Make sure you can checkout from SDSC's svn w/o having to enter a password. * Use "crontab -e" to create or edit your user crontab. (I had problems getting cron to reread my crontab when I just copied a new version to /var/cron/terri instead of using "crontab -e"). Create an entry like 10 0 * * * sh /Users/Shared/masterCIPRES.sh 1.0.1 1.0.1 > /Users/Shared/latestbuild.txt 2>&1 * Modify /misc/www/projects/TOL/dev_snapshot/index.php if you are adding a new build platform. Ideally we should have this php script under svn control and make a script adds new entries i.e. makes sure that the entries (platform, version...) in the table are correct for the build. Ultimately there should be a database storing the snapshot build info, and the web page should interact with it.