Allure Report for Azure pipelines

Official extension to generate and display embedded Allure Report 3 in Azure Pipelines

• Learn more about Allure Report at https://allurereport.org
• 📚 Documentation – discover official documentation for Allure Report
• ❓ Questions and Support – get help from the team and community
• 📢 Official annoucements – be in touch with the latest updates
• 💬 General Discussion – engage in casual conversations, share insights and ideas with the community

Usage

The extension able to render reports under 512 MB. Read more here.

To start using the extension simply add next lines to your pipeline file:

- task: PublishAllureReport@2
  displayName: "publish allure report"

This will generate Allure Report from test results stored in default directory allure-results and publish it under the name Allure Report.

- task: PublishAllureReport@2
  displayName: "publish allure report"
  inputs:
    # Directory with already generated report
    # If specified, the extension tries to publish already generated reports
    # instead of generating a new one
    # The parameter has a higher priority than `testResultsDir`
    # Default: ""
    reportDir: ""
    # Directory where test results are stored in
    # Default: "allure-results"
    testResultsDir: ""
    # Name of the report to display in Azure Pipelines UI
    # Default: "Allure Report"
    reportName: ""
    # Use it if you want to use Allure Report 2 instead of Allure Report 3
    # To use bundled Allure 2 version set input to `2.34.1`.
    # Don't use Allure Report version lower than `2.25.0` due to the single
    # file mode was introduced in this version!
    # Default: ""
    allureVersion: ""
    # Use it if you want to install Allure 2 from custom source
    # By default, the extension uses GitHub releases to download Allure Report 2
    # Default: "https://github.com/allure-framework/allure2/releases/download/{{allureVersion}}/allure-{{allureVersion}}.tgz"
    allureDownloadUrl: ""

Scenarios

Using separate reports

If you want generate completely different reports and publish them separately in a single pipeline context – just add multiple tasks with different inputs:

- task: PublishAllureReport@2
  displayName: "generate and publish new allure report"
  inputs:
    testResultsDir: "path/to/allure-results"
    reportName: "Report 1"

- task: PublishAllureReport@2
  displayName: "publish already generated allure report"
  inputs:
    reportDir: "path/to/already-generated-report"
    reportName: "Report 2"

After publish both reports will be available in the Allure Report tab of the pipeline run.