Microsoft© Team Foundation Server 2008 install bits.
Upon starting the setup process, the following screen is shown with a list of options. For the build server, select Team Foundation Build and click Install.
The next screen is Microsoft asking to record and report any issue with the install experience. Pick your preference and click Next.
Of course, thoroughly read the EULA and if you accept, check the box and click Next.
Next up is the System Health Check. If you don’t meet any of the prerequisites, follow the instructions provided.
The default folder is shown below (on Windows 7 64-bit).
The Visual Studio Team Foundation Build service will run as a typical Windows Service, which can be found through Control Panel –> Administrative Tools –> Services. As noted in the screen shot, this should not be a user account. Create an account specifically for Team Foundation Build and set your password policies as appropriate. Remember, if the password expires on the account, the service Logon property will need to be updated. If the account’s password is invalid, all builds will fail.
A confirmation screen will show before proceeding.
After the typical progress bar screen and upon successful installation, the following will be shown. Be sure to check for any updates and install them as appropriate.
By going to Control Panel –> Administrative Tools –> Services, the newly installed Visual Studio Team Foundation Build service can be seen. The default values after install are shown, which have the service start automatically.
This service operates using HTTP, which means it’s dependent on the HTTP service.
If your build server will be working with solutions created using the .NET v4 Framework, the following adjustments need to be made. This also requires installing the .NET v4 Framework on the build server. Within the file C:Program Files (x86)Microsoft Visual Studio 9.0Common7IDEPrivateAssembliestfsbuildservice.exe.config, adjust the following setting.
Remember to keep the build server clean. The definition of clean should be that only the absolutely required software be installed. Third party tools should be included in the solution, if possible. One of the goals of continuous integration is to allow a new team member to join, get latest from source control and start working. The build server gets a fresh copy from source control every time a build is done to help simulate this process. I would imagine most people are familiar with the phrase “But it works on my machine” and keeping the build server clean is a great step toward eliminating that issue.
What should be installed then? Typically, Visual Studio if you’re going to take advantage of Automated Unit Testing and Code Analysis. Things like the Silverlight tools may be required too, depending on your application.