The following plugin provides functionality available through
Pipeline-compatible steps. Read more about how to integrate steps into your
Pipeline in the
Steps
section of the
Pipeline Syntax
page.
For a list of other such plugins, see the
Pipeline Steps Reference
page.
HTML Publisher plugin
publishHTML
: Publish HTML reports
target
Nested Object
reportName : String
The name of the report to display for the build/project, such as "Code Coverage"
reportDir : String
The path to the HTML report directory relative to the workspace.
reportFiles : String
The file(s) to provide links inside the report directory
keepAll : boolean
If checked, archive reports for all successful builds, otherwise only the most recent
alwaysLinkToLastBuild : boolean
If this control and "Keep past HTML reports" are checked, publish the link on project level even if build failed.
allowMissing : boolean
If checked, will allow report to be missing and build will not fail on missing report
escapeUnderscores : boolean
(optional)
If checked, underscores in the report title will be escaped to '_5f' when stored on disk. If unchecked, they will not be escaped.
includes : String
(optional)
numberOfWorkers : int
(optional)
By default, the report files are published sequentially. If this option is provided, the report files will be published using the given number of workers.
reportTitles : String
(optional)
The optional title(s) for the report files, which will be used as the tab names. If this is not provided, file names will be used instead.
useWrapperFileDirectly : boolean
(optional)
By default, each archived reports access generates a new wrapper file. If checked, the legacy wrapper file will be used instead of generate it each time. Must only be used if wrapper file was been transformed and saved with checksum
Was this page helpful?
Please submit your feedback about this page through this
quick form.
Alternatively, if you don't wish to complete the quick form, you can simply
indicate if you found this page helpful?
See existing feedback here.