Manual BuildMaster Installation

BuildMaster consists of four main deployable components:

• Web Application – the primary interface to BuildMaster
• Service – running aside the web application, the BuildMaster Service is a Windows Service that performs tasks requested through the Web Application
• Database – a SQL Server database which stores the state and history
• Agent – a light-weight application installed on servers in which BuildMaster can manage and orchestrate

Installation

Prior to installation of BuildMaster or a BuildMaster Agent, a BuildMaster “home” directory needs to be created. We recommend C:\BuildMaster (or a similarly rooted path) because a number of 3rd-party tools that BuildMaster integrates with have issues with very long path names.

For the remainder of these instructions, we will use C:\BuildMaster as the root - replace with the specific path you have chosen for your installation as necessary.

BuildMaster's Identity

BuildMaster may be configured to use its own domain account or may run as NETWORK SERVICE or LOCAL SYSTEM. While not required, administrator-level privileges are strongly recommended as it will eliminate any difficulty or confusion with moving files and running different actions.

Database Installation

1. Create a database called BuildMaster on the desired server
2. Unzip BuildMaster-DbChangeScripts.zip into any directory an run the executable and select option 3 (update). Note: if you are not running SQL Server using the Default Instance or you are not running the .exe on the same server as the database engine, you will have to manually update the connection string within the bmdbupdate executable by choosing option “C” prior to updating.
3. Unzip BuildMaster-DbObjects.zip into any directory and run batchsql.bat. Note: if you are not running SQL Server using the Default Instance or you are not running the .exe on the same server as the database engine, you will have to manually update the connection string within the batchsql.bat file.

Web Application Installation

1. Create a directory called WebApp\ under C:\BuildMaster\
2. Unzip BuildMaster-WebApp.zip into C:\BuildMaster\WebApp\
3. Create a directory called _WEBTMP\ under C:\BuildMaster\
4. Edit Web_appSettings.config to ensure two settings:
   • Core.DbConnectionString (if on remote server or different instance)
   • Core.BaseWorkingDirectory (if different from default)
5. Create an application pool in IIS to run under the appropriate identity; for IIS7 and later, a classic (non-integrated) pipeline should be used
6. Create a website that points to C:\BuildMaster\WebApp using whichever host name configuration or ports preferred. Note: A virtual directory is not supported at this time. Note: If IIS6 is used, verify that the website is configured for ASP.NET 2.0.

Service Installation

1. Create a directory called Service\ under C:\BuildMaster\
2. Unzip BuildMaster-Service.zip into C:\BuildMaster\Service\
3. Create a directory called _SVCTMP\ under C:\BuildMaster\
4. Edit App_appSettings.config to ensure two settings:
   • Core.DbConnectionString (if on remote server or different instance)
   • Core.BaseWorkingDirectory (if different from default)
5. Install the service by running “bmservice.exe /i”

Extensions

1. Create a directory called Extensions\ under C:\BuildMaster\
2. Unzip BuildMaster-Extensions.zip into C:\BuildMaster\Extensions

Remote Agent Servers

1. Create a directory called Agent\ under C:\BuildMaster\
2. Unzip BuildMaster-Agent.zip into C:\BuildMaster\Agent\
3. Create a directory called _AGTTMP\ under C:\BuildMaster\
4. Edit Web_appSettings.config to ensure one setting:
   • Core.BaseWorkingDirectory (if different)
5. Create an application pool in IIS to run under the appropriate identity; for IIS7 and later, a classic (non-integrated) pipeline should be used
6. Create a website that points to C:\BuildMaster\Agent using whichever host name configuration or ports preferred. Note: A virtual directory is not supported at this time. Note: If IIS6 is used, verify that the website is configured to support ASP.NET 2.0 applications.