Overview of the Build Details Web Page

  • Article

Team Foundation Build can be configured to include a Team Foundation Build details Web page that can be viewed over the Internet. Team members can use this Web page remotely to check the status of builds. The Web page can also be associated with build notification e-mail messages. For more information, see How to: Receive Build Notification E-Mail.

Team Foundation Build Details Web Page Sections

The Team Foundation Build details Web page contains the following five sections:

  • Summary

  • Build steps

  • Result details

  • Associated changesets

  • Associated work items

Summary

The summary section contains the build name, team project, build definition, computer, and the following information.

Summary item

Description

Example output

Build name

Indicates the name of the build and links to the drop location where the built binaries are available.

Nightly 050615.00

Requested by

Indicates the name of the user requesting the build.

Domain\username

Team project

Indicates the name of the team project.

Tour Package Service v2.2

Definition name

Indicates the name of the build definition that ran.

Nightly

Agent name

Indicates the name of the build agent specified for the build definition.

AdventureWorks_BuildLab01

Command-line arguments

Command-line arguments, if any, associated with this build definition.

/verbosity:detailed

Started on

Indicates the date and time stamp when the build started.

06/20/2008 03:00:00 AM

Completed on

Indicates the date and time stamp when the build completed.

06/20/2008 03:22:10 AM

Last changed by

Indicates the name of the user that last changed the build.

Domain\username

Last changed on

Indicates the date and time stamp when the build was last changed.

06/20/2008 03:22:10 AM

Quality

Indicates the quality of the build.

Unexamined

Work items opened

Indicates the work items created because of the build processing.

Bug 1234 (Active/Unassigned)

Source control version

Source control version of the files that are being built.

C27

Log

Indicates the path of the build log.

\\Builds\drops\nightlybuilds\20050620.00\logfiles\buildlog.txt

Custom task events

Indicates the path of the custom task events.

\\Builds\drops\nightlybuilds\20050620.00\logfiles\customtasks.xml

Build Steps

The build steps section displays the steps associated with the build definition that was run during the build process. The actual output varies depending on the files associated with the build definition, and also upon the success of the build. The build steps also include date and time stamp indicators, such as 06/20/2008 03:00.00. The build steps include the following:

  • Initializing build

  • Getting sources

  • Compiling sources

  • Compiling <Solution Name> for <Platform>/<Flavor>

  • Compiling <Project Name>

  • Running tests

  • 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

  • Copying log files to drop location

  • Succeeded

  • Failed

  • Stopped

Result Details

The result details section displays error and warning messages associated with specific build configurations. For example, x86/Debug.

Details Item

Description

Example output

Result details for x86/Debug

Indicates the number of errors and warnings, test results, and coverage results associated with the platform/configuration combination that was run.

4 Errors, 12 warnings, no test results, no coverage results (X86Debug.error)

Result details for x86/Retail

Indicates the number of errors and warnings, test results, and coverage results associated with the built type that was run.

0 Errors, 10 warnings, 8/10 tests passed, 42% lines covered (X86Retail.error)

Associated Changesets

The associated changesets section displays information about which changesets are associated with the build and who checked them in.

Associated Changesets Item

Example output

1001

Checked in by: Jdoe

Comments: Updated AddTo_ and RemoveFromShoppingCart.

1002

Checked in by: Jdoe

Comments: Updated business logic per requirement 1.

1003

Checked in by: Jdoe

Comments: Updated business logic per requirement 2.

Associated Work Items

The associated work items section displays information about which work items are associated with the build and who checked them in.

Associated Work Item

Example output

3479

Title: Add AppDiscount Web Service method

Check-in Action: Associated

Changed by: Jdoe.

Log File

In the Service Pack 1 Edition of Microsoft Visual Studio Team System 2008 Team Foundation Server, the log file contains a Reason property that lists the build trigger that was used for the build. The values are:

  • Manual   The build was queued manually.

  • IndividualCI   A continuous integration build that was set to build after each check-in.

  • BatchedCI   A continuous integration build that was set to build after a batch check-in.

  • Schedule   A scheduled build.

  • ScheduleForced   A scheduled build that was started without having any new changes checked in.

  • For more information, see Reason Property.

See Also

Tasks

How to: Receive Build Notification E-Mail

Concepts

Overview of Build Reports

Other Resources

Running Builds in Team Foundation Build