You are viewing the documentation of TeamCity 8.x, which is not the most recently released version of TeamCity.
View this page in TeamCity 2018.x documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.


Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0


The general flow is as follows:

  • configure the build script to produce the HTML report (preferably in a zip archive);
  • configure build artifacts to publish the report as the build artifact to the server: at this point you can check that the archive is available in the build artifacts;
  • configure the Report Tab to make the report available as an extra tab on the build or project level as described here if you are running TeamCity 8.1 or above; for versions earlier than 8.1, refer to this section.


Starting from TeamCity 8.1, report tabs support project hierarchy. There are two types of tabs available:




Tab Title

Specify a unique title of the report tab that will be displayed in the web UI.

Get artifacts from

This field is available for project-specific report tabs only
Specify the build whose artifacts will be shown on the tab. Select whether the report should be taken from last successful, pinned, finished build or build with specified build number or last build with a specified tag.

Start page

Specify the path to the artifacts to be displayed as the contents of the report page. The path must be relative to the root of the build artifact directory. To use a file from an archive, use the path-to-archive!relative-path syntax, e.g. javadoc.zip!index.html. See the list of supported archives.

See also:


Wiki Markup