If your reporting tool produces reports in HTML format, you can extend TeamCity with a custom tab to show the information provided by the third-party reporting tool.
The report provided by your tool can be then displayed either on the build results page, or on the project home page.

The general flow is as follows:


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

To configure a report tab, go to the Project Settings| Report Tabs page, click Create new report tab and proceed with the following options:

Option

Description

Report tab type

Type of the report tab (Build or Project-level)

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.


Prior to TeamCity 8.1, the behavior is slightly different:

There are two types of report tabs available:

To configure a report tab, go to the Integrations | Report Tabs page |(for the build-level tab) or project settings (for a project-level tab), click Create new report tab and proceed with the following options:

Option

Description

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:

{show-if}{show-if}