You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Configuration Reports

Configuration reports allow you to link a set of reports to a configuration. This allows you to view build associated reports from within Continua CI's build view.

For example, if you have included code coverage as part of your build, then the associated code coverage report can be linked to that specific build and easily viewed through the Continua CI UI. 

Configuration reports support any file type that can be rendered through the browser including, but not limited to .html, .xml and .txt files.

Configuration Reports Setup

Reports can be linked up to a Configuration through the Configuration Wizard, under the Reports section.

 

Configuration Report Options

Name

The name Continua CI will use to identify the report.

Report Filename

The location of the root file of the report. This is the initial page that will be displayed when viewing the report.

For example, if it is a HTML report then this is usually default.html or index.html.

This field also allows Variables, Objects & Expressions to be used. This means that you can specify the file location based on the builds workspace.

For example, if your code coverage report was saved in your output folder of the workspace then the path would be $Workspace$/Output/codeCoverageReport/index.html

It is recommended that all reports are stored and referenced using the $Workspace$ which allows all reports to be stored and associated with each individual build.

Enabled

Only enabled reports will be displayed on builds.

Description

Provide extra information regarding the report. this information is shown when you hover over its report tab in the build.

Help! My Report is missing from the $Workspace$ directory

If your report is being generated on an agent but it is missing from the Continua Workspace then the report may not be getting copied from the agent to the server correctly.

This can be checked and edited in the Workspace Rules for each Stage in the Stages editor. Make sure that all the necessary folders and files have been configured to copy across back to the server.

 

  • No labels