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.

Nested Data Reporting

View this plugin on the Plugins site

publishReport: Publish report files like json, yaml, csv or xml

  • displayType : String (optional)
  • name : String (optional)
  • provider (optional)
      Nested Choice of Objects
    • csv
      • id : String (optional)
        Normally the ID of the report is read via the underlying file. With a CSV provider this is not possible, because in a csv file you have no possibility to specify it in a structured way. Therefore the CSV provider needs an ID to tag the read report and to find reports of past builds to create the history.
      • pattern : String (optional)
        A pattern is defined by an Ant Fileset ''includes'' setting that specifies the report files to scan. Multiple patterns can be separated by space or comma. Note that such a pattern is resolved in Jenkins' workspace, so the paths must be relative only.
    • json
      • id : String (optional)
        Normally the ID of the report is read via the underlying file. With a CSV provider this is not possible, because in a csv file you have no possibility to specify it in a structured way. Therefore the CSV provider needs an ID to tag the read report and to find reports of past builds to create the history.
      • pattern : String (optional)
        A pattern is defined by an Ant Fileset ''includes'' setting that specifies the report files to scan. Multiple patterns can be separated by space or comma. Note that such a pattern is resolved in Jenkins' workspace, so the paths must be relative only.
    • xml
      • id : String (optional)
        Normally the ID of the report is read via the underlying file. With a CSV provider this is not possible, because in a csv file you have no possibility to specify it in a structured way. Therefore the CSV provider needs an ID to tag the read report and to find reports of past builds to create the history.
      • pattern : String (optional)
        A pattern is defined by an Ant Fileset ''includes'' setting that specifies the report files to scan. Multiple patterns can be separated by space or comma. Note that such a pattern is resolved in Jenkins' workspace, so the paths must be relative only.
    • yaml
      • id : String (optional)
        Normally the ID of the report is read via the underlying file. With a CSV provider this is not possible, because in a csv file you have no possibility to specify it in a structured way. Therefore the CSV provider needs an ID to tag the read report and to find reports of past builds to create the history.
      • pattern : String (optional)
        A pattern is defined by an Ant Fileset ''includes'' setting that specifies the report files to scan. Multiple patterns can be separated by space or comma. Note that such a pattern is resolved in Jenkins' workspace, so the paths must be relative only.

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.