Changes between Version 25 and Version 26 of BuildServerSetup

Timestamp:

Jul 26, 2009, 9:10:41 PM (15 years ago)

Author:

Philip Taylor

Comment:

partially update autobuilder description

BuildServerSetup

@@ -6 +6 @@
 
  * The server runs on [http://aws.amazon.com/ec2/ Amazon EC2].
- * The server has Windows Server 2003, VC++ 2008, SVN, Perl, and nothing else installed.
+ * The server has Windows Server 2003, VC++ 2008, SVN, Perl, and little else installed.
  * The server has a persistent [http://aws.amazon.com/ebs/ EBS] disk with the SVN checkout.
- * On startup, the server runs a script. The script updates SVN, builds, saves the log output somewhere, and if it was successful then it commits the new binaries.
- * Some other server runs some kind of script that provides an authenticated web interface to (re)start the build server, and terminates it after some period of time when it's done.
+ * On startup, the server runs a script. The script updates SVN, builds, saves the log output to S3, and if it was successful then it commits the new binaries.
+ * A permanent non-Windows server runs some scripts that provide an authenticated web interface to (re)start the build server, and terminate it after some period of time when it's done.
 
 All code is [source:/ps/trunk/source/tools/autobuild2 available in SVN]. (Only configuration files with private data are excluded.)
@@ -23 +23 @@
  * Install [http://downloads.activestate.com/ActivePerl/Windows/5.10/ActivePerl-5.10.0.1004-MSWin32-x86-287188.msi ActivePerl].
  * Install [http://search.cpan.org/~jkim/Net-Amazon-EC2-0.09/ Net::Amazon::EC2], [http://search.cpan.org/~tima/Amazon-S3-0.441/ Amazon::S3], DateTime::Format::ISO8601 using the Perl Package Manager.
- * Download [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx SDelete], extract into `c:\bin`.
- * Download [http://technet.microsoft.com/en-us/sysinternals/bb897438.aspx Sync], extract into `c:\bin`.
- * Create the registry key `HKEY_USERS\S-1-5-18\Software\Sysinternals\Sync`, set DWORD `EulaAccepted` = `1`. (Yay.)
+ * Download [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx SDelete], extract into `c:\bin`
+ * Download [http://technet.microsoft.com/en-us/sysinternals/bb897438.aspx Sync], extract into `c:\bin`
+ * Create the registry key `HKEY_USERS\S-1-5-18\Software\Sysinternals\Sync`, set DWORD `EulaAccepted` = `1`
  * Attach the EBS disk.
  * If the disk hasn't been set up already: Administrative Tools -> Computer Management -> Disk Management -> Disk 2 -> Initialize Disk, New Partition -> drive letter E.
@@ -35 +35 @@
  * Set up `c:\0ad\autobuild\aws.conf`:
   * `aws_access_key_id`, `aws_secret_access_key` are from your Amazon account.
- * Set up the build runner server's `run.conf` (which will be copied to the build server on startup):
+ * Set up the build-runner server's `run.conf` (which will be copied to the build server on startup):
   * `ebs_volume_id` is from the EBS volume you created.
   * `svn_username`, `svn_password` are the SVN login details.
@@ -45 +45 @@
   * Defragment drive C.
   * `c:\bin\sdelete -c c:`
-  * Bundle into `s3://wfg-autobuild-images/vc2008`.
+  * Bundle into `s3://wfg-autobuild-images/vc2008`
   * Register the bundle as an AMI.
  * Set up `manage.conf` on the build-runner server:
@@ -52 +52 @@
 == Build script ==
 
-The initial part (stored on the image on S3) does something like:
- * `ec2-attach-volume` to attach the EBS disk.
+The [source:ps/trunk/source/tools/autobuild2/startup.pl startup.pl] script (stored on the image on S3) does the following:
+ * Create `d:\0ad`. (The script might run before the data disk has been mounted on `d:`, so it repeats until it's successful.)
+ * Download the EC2 ''user data'' resource, then unzip it and execute its `run.pl`.
+The ''user data'' contains [source:ps/trunk/source/tools/autobuild2/run.pl run.pl] and [source:ps/trunk/source/tools/autobuild2/run.conf run.conf.example], uploaded by the build-runner script. `startup.pl` is hard to modify (since it's frozen into the bundle), so it does as little as possible and defers to `run.pl` for most of the work.
+
+`run.pl` does something like:
+ * Start writing logs on S3.
+ * Attach the EBS disk to the machine.
  * `svn up` on the EBS disk.
- * Run the rest of the build script from the SVN directory.
-The rest of the build script does:
+ * Run the rest of the build script (`build.pl`) from the SVN directory.
+ * Shut down the machine.
+
+`build.pl` does:
  * (TODO: is it more efficient if all the source is copied onto the local disk before compiling?)
  * `premake --target vs2008 --outpath e:\build`