Allure 3 should work on Azure devops pipeline?

[mircea2487]

Hello,

I am using Allure for reporting in my Playwright (TypeScript) framework. After updating to Allure extension to 2.0.1, the documentation suggests that Allure Report 3 should be supported and viewable directly in Azure DevOps Pipelines.

I updated all relevant configurations accordingly, however, when running the pipeline in Azure DevOps, the Allure report is still not displayed as expected. Instead, I receive the following issue in ADO:

Could you please confirm:

• whether Allure Report 3 is fully supported in Azure DevOps Pipelines,

• and if any additional configuration or pipeline steps are required to correctly publish and view the report?

Thank you.

[Rubaka]

Actually a right question, as v3 now official stable, but don't see any confirmation about CI/CD support in Azure?

[epszaw]

Hello! Yes, the extension should support Allure 3 and utilizes it by default.
You can find updated reference here: https://marketplace.visualstudio.com/items?itemName=qameta.allure-azure-pipelines
In case you want to use Allure 2 instead of 3 – add explicitly allureVersion input.
If you generate allure report during test process – add reportDir input and the extension will upload the report directly.
If you don't generate allure report, but have allure results to generate the report from – add testResultsDir input and the extension will generate and publish the report.

[epszaw]

Hello! Yes, I have an idea and tried to resolve the problem. Please try to use the latest version of the extension (>=2.1.2), it should work properly now.

[ciconq]

Hello @epszaw, thank you for your response. Currently the PublishAllureReport@2 task is passing successfully but when I try to open the Allure Report tab I get the same error message as the author of the thread(cannot see any failed requests in the Network tab).
I don't think anything changed from Allure2 in Allure3 related to how you pass the allure-results directory? Because I haven't made any changes there as it was working with Allure2. At least in the logs for the the PublishAllureReport@1 task I can see if there were test results files found, in the PublishAllureReport@2 task there is nothing which makes me think it doesn't find the test results files.

Also I am not sure why in the extensions section Allure Report is shown with the correct version which is 2.1.2(latest) and under the official page for AzureDevOps extensions it is shown with version 2.1.3 but I guess this is not related or there was a new version.

[ciconq]

Hello @epszaw, do you have an idea why the report is not generated even if the PublishAllureReport@2 task is passing successfully?
I have tried with the following inputs for testResultsDir:

1. '$(System.DefaultWorkingDirectory)/allure-results'(this is specified as the 'resultsFolder' in my VSTest@2 task)
2. '$(allureResultsPath)' - this variable is set with a previous task which is searching recursively for allure-results directory
3. No input at all in order to use the default value for 'testResultsDir' which is 'allure-results'

For all those 3 inputs that I have tried the PublishAllureReport@2 task is passing successfully but without generating any report.

This is the output of the task after it has ran successfully:

2026-02-17T12:46:15.3466018Z ##[section]Starting: Publish allure report
2026-02-17T12:46:15.3473543Z ==============================================================================
2026-02-17T12:46:15.3473672Z Task         : Publish Allure Report
2026-02-17T12:46:15.3473736Z Description  : Task for generate and publish Allure Report
2026-02-17T12:46:15.3473818Z Version      : 2.1.4
2026-02-17T12:46:15.3473882Z Author       : Qameta Software Inc.
2026-02-17T12:46:15.3473944Z Help         : Generate and publish Allure Report
2026-02-17T12:46:15.3474014Z ==============================================================================
2026-02-17T12:46:16.4471435Z ##[section]Finishing: Publish allure report

Normally with Allure2 I get additional logging like how many test files are found, downloading packages, caching, prepending PATH environment variable with a given directory and finally that the Allure Report was successfully generated at a given directory.

Thank you for your attention and time!

[krypton1981]

I am getting the same error when using PublishAllureReport@2 to generate an Allure3 report but the error goes away when I set allureVersion: 2.36.0 to force it back to Allure2 with PublishAllureReport@2

[epszaw]

Ok, I'm going to add more logs for debugging and one more input to be able to turn-on or turn-off the information logging.

[andjb]

I don't know how relevant this answer will be, but I have been battling with getting allure 3 reports into an azure pipe all day, and have just succeeded (...initially... history tbc)

I am running playwright, with the following depemdencies:
"devDependencies": {
"@playwright/test": "^1.56.0",
"@types/node": "^24.7.2",
"allure": "^3.2.0",
"allure-playwright": "^3.4.2"

My yaml is attached

azure_pipe_playwright.yml

[ciconq]

Hey @andjb, thank you for your suggestion, glad it worked for you. A reason that it works might be that you are using an ubuntu agent? I am using a self-hosted windows agent, maybe there is an issue with windows agents, no idea, just an assumption. The case is the same for me as @krypton1981 mentioned, if I downgrade to Allure2, it is working but not working for Allure3. I am using a separate task that is fetching the allure-results directory, this is because of how VSTest task works and cleans the default resultsFolder but this shouldn't be a problem because it works for Allure2.

[krypton1981]

Yes, I missed the agent detail @ciconq. I am using windows-latest and it is not self hosted just the default one from Microsoft.

[epszaw]

Did you generate the report in the single file mode? The extension supports only this mode, rest reports won't be published.

You can make a quick check in the pipeline's log. If it contains similar lines:

Report "Allure 3 Report" hasn't been generated in the single-file mode, skipping upload
Report "My Dashboard" hasn't been generated in the single-file mode, skipping upload

It means you need to turn on single file mode.

If the mode is turned on – please, let me know.

[ciconq]

There is nothing but this output for the PublishAllureReport@2 task:

2026-02-03T11:21:09.9080593Z ##[section]Starting: Publish allure report
2026-02-03T11:21:09.9088243Z ==============================================================================
2026-02-03T11:21:09.9088373Z Task         : Publish Allure Report
2026-02-03T11:21:09.9088436Z Description  : Task for generate and publish Allure Report
2026-02-03T11:21:09.9088517Z Version      : 2.1.4
2026-02-03T11:21:09.9088581Z Author       : Qameta Software Inc.
2026-02-03T11:21:09.9088656Z Help         : Generate and publish Allure Report
2026-02-03T11:21:09.9088728Z ==============================================================================
2026-02-03T11:21:11.3152845Z ##[section]Finishing: Publish allure report

[krypton1981]

@epszaw not sure what the right process for generating single file using the PublishAllureReport@2 task, is there documentation on this?