This setting specifies a list of additional attributes for metric results.
A list of comma separated attribute. The following attributes are supported by default:
This setting enables or disables archiving reports into a ZIP file.
|true||Reports are archived in a ZIP file.|
|false||Reports are not archived in a ZIP file.|
This setting specifies the start date for trend graphs that track static analysis task, test execution, and coverage. Requires configuring the
A date in the month-day-year format.
This setting specifies the duration from the start date for trend graphs that track static analysis task, test execution, and coverage. Requires configuring the
Specifies the duration in the days-months-years format.
This setting enables or disables report emails to developers and additional recipients specified with the
|true||Developers and additional recipients are automatically sent a report that contains the errors/results related to his or her work.|
|false||Default. Developers and additional recipients are not sent the reports.|
This setting specifies the mail server used to send reports.
The host name of the server where the report will be sent.
This setting specifies the port for SMTP server.
The port number. The default is
This setting specifies SMTP server connection security.
|STARTTLS||Default. STARTTLS connections security is used.|
|SSL||SSL connections security is used.|
This setting specifies the subject line of the emails that are sent.
The subject of the email.
report.mail.subject=ABC Project Results
These settings specify required information for SMTP server authentication. The realm value is required only for those servers that authenticate using SASL realm.
This setting specifies the mail domain used to send reports.
The domain where the reports are sent.
This setting specifies a delay between emailing reports (to avoid bulk email restrictions).
The reports will be emailed with the specified time delay.
This setting specifies the content of the "from" field of the emails sent.
|[email]||The "from" field will include the email address|
|[user]||The "from" field will include the user name.|
This setting enables or disables sending reports as attachments. All components are included as attachments; before you can view a report with images, all attachments must be saved to the disk.
|true||The emails will be sent with attachments.|
|false||The emails will be sent without attachments.|
This setting specifies how the report information is delivered in the email. This setting is not configured by default.
|trends||The email contains a trend graph, summary tables, and other compact data; detailed data is not included|
|links||The email only contains a link to a report available on DTP server.|
This setting specifies the content type for the email.
|html||The email content has the HTML format.|
|ascii||The email content has the ASCII format.|
This setting specifies email address for sending comprehensive manager reports. Multiple addresses must be separated with a semicolon. This setting is commonly used to send reports to managers or architects, as well as select developers.
A list of email addresses separated by semi-colons.
This setting specifies email addresses of developers that you want to receive developer reports. Multiple addresses must be separated by a semicolon. This setting is commonly used to send developer reports to developers if developer reports are not sent automatically (e.g., because the team is not using a supported source control system).
This setting overrides addresses specified in the 'exclude' list.
A list of email addresses separated by semi-colons.
This setting specifies email addresses that should be excluded from automatically receiving reports.
A list of email addresses separated by semicolons.
This setting enables or disables report emails to developers who are not explicitly listed in the
report.mail.cc setting. This setting is used to prevent reports from being mailed to individual developers.
|true||Emails will not be sent to developers who are not explicitly specified.|
|false||Default. Developers are not excluded from the mailing list.|
This setting specifies where to email reports for errors assigned to "unknown".
|[email]||The reports assigned to t"unknown" are sent to the specified email address.|
|[user]||The reports assigned to t"unknown" are sent to the specified user.|
This setting enables or disables email reports to the manager when an error is found or a fatal exception occurs. Developer emails are not affected by this setting; developer emails are sent only to developers who are responsible for reported errors.
|true||Emails with specific information about errors and fatal exceptions are sent to the manager.|
|false||Default. Emails with specific information about errors and fatal exceptions are not sent to the manager.|
This setting specifies where the Setup Problems section is placed in the report.
|top||The Setup Problems section is placed at the top of the report.|
|bottom||Default. The Setup Problems section is placed at the bottom of the report.|
|hidden||The Setup Problems section is not displayed in the report.|
This setting specifies a limit to the number of messages reported in a single setup problem category.
The maximum number of messages reported in a single setup problem category. The default value is
This setting specifies a limit to the total number of messages displayed in the HTML report in the setup problem section.
The maximum number of the total number of messages reported in the Setup Problem section. The default value is
This setting specifies whether setup problems will be printed on the console.
|true||Default. Setup problems are printed to the console.|
|false||Setup problems are printed to the console.|
This setting specifies the type of coverage included in an additional report, which includes source code annotated with line-by-line coverage details when a test's HTML report links to it.
|LC||Line coverage is included in the report.|
|DC||Decision coverage is included in the report.|
This setting specifies how much memory should be used for reports generation.
The maximum amount of memory allocated for report generation. The default is
This setting enables or disables generating reports as a separate virtual machine.
|true||Reports are generated as a separate virtual machine.|
|false||Default. Generating reports as a separate virtual machine is disabled.|
This setting specifies the path to launch file that should be used during reports generation.
The path to the launch file.
This setting specifies how elements in the code duplication findings are sorted.
|oldest||The oldest result is displayed at the top.|
|newests||The newest result is displayed at the top.|
|paths||Default. The results are sorted by full path names in the ascending alphabetical order (A to Z).|
This setting specifies the version of the XML coverage report.
|1||Default. The standard version is used.|
|2||The size of the XML report is optimized.|
This setting determines whether the current installation of the product reports results of local analysis to the DTP server.
The results are published to DTP.
|false||Default. The results are not published to DTP.|
The following configuration enables sending local analysis results to DTP.
This setting specifies whether the tested source code is published to the DTP server.
|off||Source code is not published to DTP. Default when the report.dtp.publish option is enabled.|
|min||The minimal part of the source code is published (in most cases, source code without reference to source control, for example, auto-generated code, is published.|
All of the source code from the specified scope is published to DTP. Default when the report.dtp.publish option is enabled.
The following configuration enables partial publishing of source code to DTP.