Changes between Version 70 and Version 71 of RunningBuildbotOnWindows

Timestamp:

09/16/11 09:56:48 (20 months ago)

Author:

philippem

Comment:

--

RunningBuildbotOnWindows

@@ -13 +13 @@
 For the remainder of this document we will assume python was installed in "`C:Python26`".  Please adjust accordingly if you install to a different path.
 
-Install python, pywin32, and Twisted for all users.  On Windows Server 2003 it was found that this MUST be done while logged in as the actual "Administrator" account, NOT as a regular user with Administrator privileges, because of the way filesystem permissions are inherited during egg installation. The buildbot service itself need not be a privileged account (see below). When running python setup.py, be sure to use the full path to the version of python you expect to run buildbot (It is ok to have multiple versions of python installed).  The pywin32 and Twisted installers will be matched for the version of python that will be running buildbot.
+Install python, pywin32, and Twisted for all users.  On Windows Server 2003 it was found that this MUST be done while logged in as the actual "Administrator" account, NOT as a regular user with Administrator privileges, because of the way filesystem permissions are inherited during egg installation. '''The buildbot service itself need not be, and probably should not be, a privileged account (see below).''' When running python setup.py, be sure to use the full path to the version of python you expect to run buildbot (It is ok to have multiple versions of python installed).  The pywin32 and Twisted installers will be matched for the version of python that will be running buildbot.
 
 Install Buildbot itself with
@@ -116 +116 @@
 }}}
 
+Consider using vms to manage your slaves. Create a clean base installation and clone it for each new build configuration or build requirement.
+
 Restart the service and your new buildslaves will connect.