Working with Build Results

Skip to end of metadata
Go to start of metadata
You are viewing documentation of TeamCity 7.x, which is not the most recently released version of TeamCity. Please refer to the listing to choose another version.
Search

Searching TeamCity 7.x Documentation

Table of Contents

In TeamCity all information about particular build, regardless if it's still running or already finished, is accumulated on so-called build results page. However, some data is accessible only after the build is finished. Build results can be accessed from various places in TeamCity web UI, for example, from Build Configuration home page:

In addition to the general information about the build, like build duration, agent used, trigger, etc., build results page also contains following useful information:

If another build of this same build configuration is concurrently running, a small window appears on the Overview tab with the following information:
  • The build results of that build linking to the build results page;
  • A changes link with a drop-down list of changes included in that build;
  • The build number, time of start, and a link to the agent it is running on.
If a build is probably hanging, the corresponding notification is displayed on top of the Overview tab of the build results. Moreover, in this case TeamCity provides a link to view the process tree of the running build, and thread dumps of each Java or .Net process in a separate frame. If the process is not Java or .Net, its command line is retrieved. The possibility to view thread dump is supported for the following platforms:
  • Windows, with JDK 1.3 and higher
  • Windows, with JDK 1.6 and higher, using jstack utility
  • Non-Windows, with JDK 1.5 and higher, using jstack utility

Tests Failed in the Build

If the build has failed tests, you can view them right on the Overview tab of the build results page:

For each failed you can jump to its history, assign a team member to investigate its failure, open the test in your IDE to start fixing it right away.
Moreover, all tests are displayed in the dedicated Tests tab. Learn more.

Changes Included in Build

Not only you can review changes included in build, from the Changes tab you can also:

For each particular change you can (when expanded):

Build Log

For each build you can view and download its build log in preferable way:

Build Parameters

All system properties and environmental variables which were used by the particular build are listed on the Build Parameters tab of the build results. Learn more about build parameters.

Dependencies

If the finished build has artifact and/or source dependencies, the Dependencies tab is displayed on the build results page, where you can explore builds which artifacts and/or sources were used for creating the particular build as well as the builds which used the artifacts and/or sources of the current build.
Additionally you can opt to view indirect dependencies for the build. That is, for example, if a build A depends on a build B which depends on builds C and D, then these builds C and D are indirect dependencies for the build A.

Related Issues

If you have the issue tracker integration configured, and there is at least one issue mentioned in the comments for included changes or in the comments for the build itself, you'll see the list of issues related to the current build in the Issues tab.
If you need to view all the issues related to a build configuration and not just for particular build, you can navigate to the Issues Log tab available on the build configuration home page, where you can all the issues mapped to the comments or filter the list to particular range of builds.

Build Artifacts

If the build has produced some artifacts, they are accumulated at the dedicated Artifacts tab.

Code Coverage Results

If you have code coverage configured in your build runner, dedicated tab appears in build results that shows the full HTML code coverage report.

Code Inspection Results

The results of the Code Inspection build step are gathered at the Code Inspection tab in the build results.

Use the left pane to navigate through inspection results, the filtered inspections are shown in the right pane.

  • Switch from Total to Errors option , if you're not interested in warnings.
  • Use scope filter to limit the view to the specific directories. This makes it easier for developers to manage specific code of interest.
  • Use the inspections tree view under the scope filter to display results by specific inspection.
  • Note that TeamCity displays the source code line number that contains the problem. Click it to jump the code in your IDE.

Duplicates Found

If your build configuration has Duplicates build runner as one a build step, you will see the Duplicates tab in the build results:

The tab consists of:

  • A list of duplicates found. The new only option enables you to show only the duplicates that appeared in the latest build.
  • A list of files containing these duplicates. Use the left and right arrow buttons to show selected duplicate in the respective pane in the lower part of the tab.
  • Two panes with the source code of the file fragments that contain duplicates.
  • Scope filter in the the upper-left corner lists the specific directories that contain the duplicates. This filtering makes it easier for developers to manage specific code of interest.

Maven Build Info

For each Maven build TeamCity agent gathers Maven specific build details, that are displayed on the Maven Build Info tab of the build results after the build is finished.



See also:

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.