Overview of Build Reports
Team Foundation Build generates detailed build information for each completed build and also for builds that are in progress. You can view the build report by double-clicking the build in Build Explorer. For more information, see Understanding the Team Foundation Build Explorer and How to: View Build Summary Status.
The following tables show how the build report is categorized by sections. These categories include the following:
The following table displays the information in the Summary category in a build report.
Name of the build. The build name is based on the build definition name, a date stamp, and a sequential number. For example, MyBuildDefinition_060616.01. The build name provides a link to the drop location that contains the built binaries.
Name of the user who requests the build be produced.
Team project that has been built.
Name of the build definition that was used to generate this build.
Build agent computer where the build will run.
Command-line arguments, if any, associated with this build definition.
Date and time stamp that indicates when the build was started.
Date and time stamp that indicates when the build completed.
Last changed by
User who last changed the build.
Last changed on
Date and time stamp that indicates when the build was last changed.
Current build's quality state. This information is read-only.
Work items opened
Work items that were opened because of the compilation and static analysis errors that occurred in the build.
Source control version
Source control version of the files that are being built. For example, C27.
Link to network share where the build log is located.
In the Service Pack 1 Edition of Microsoft Visual Studio Team System 2008 Team Foundation Server, the log file contains a Reason field that lists the build trigger that was used for the build. The values are:
The following table explains the build steps category of the build report. These entries will vary depending on the build type used and whether the build was successful. The build steps also include date and time stamp indicators such as 06/20/2006 03:00.00). The build steps include the following:
Compiling <Solution Name> for <Platform>/<Flavor>
Compiling <Project Name>
Generating list of changesets and updating work items (Note Appears only on successful builds)
Getting changesets (Note Appears on build breaks)
Creating work item (Note Appears on build breaks)
Copying binaries to drop location
The following table explains the result details category of the build report. This section may not be present if the build failed due to inadequate build permissions.
Errors and Warnings
Displays a summary of the errors and warnings. If an error occurred, displays a link to a file that contains a list of the compilation errors and warnings for the operating system/configuration combination
Displays information for all tests run on the build. Each row in the table displays the following information about each test run.
Code Coverage Results
Displays the output of code coverage results.
The Associated Changesets category provides information about the changesets that are part of the build.
The section title in the report denotes the number of changesets associated with the build.
For more information, see Working with Version Control Changesets.
Number of the changeset displayed as a link. Clicking this link will show details of the check-in.
Checked In By
User who checked in the changeset.
Comments associated with the changeset.
The Associated Work Items category provides a dialog box displaying information about the work items associated with this build.
The section title in the report denotes the number of work items associated with the build.
For more information, see Working with Team Foundation Work Items.
Work item associated with this build. It is displayed as a link, and clicking this link will show details of this work item.
Title information retrieved from Team Foundation Server for this work item.
Check-in action associated with the work item.
User who associated this work item to this build.