BUG: PublishAllureReport@2 v2.2.7 ignores an omitted or explicitly empty reportDir and publishes from $(System.DefaultWorkingDirectory) #3505
Replies: 1 comment
|
This appears to have been fixed in extension version 2.2.8. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
After a forced upgrading the Azure DevOps Allure Report extension to
2.2.7,PublishAllureReport@2resolvesreportDirto$(System.DefaultWorkingDirectory)even whenreportDiris explicitly set to an empty string.This causes the task to select the publish an existing report path instead of generating a report from the supplied Allure results directory.
Environment
ubuntu-latest2.2.32.2.7Allure.Reqnroll2.15.0.NET 10Pipeline Task Configuration
merged-allure-resultsexists and contains the merged raw Allure result files from parallel test agents.Actual Behavior
The task debug output shows that
reportDiris populated despite being explicitly set to an empty string:The task then enters existing-report publishing mode:
Expected Behavior
When
reportDiris omitted or explicitly empty:PublishAllureReport@2should generate a report fromtestResultsDir.$(System.DefaultWorkingDirectory)asreportDir, nor enter existing-report publishing mode.Reproduction Steps
PublishAllureReport@2with a valid directory of raw Allure results usingtestResultsDir.reportDir, or explicitly set it to''.2.2.7.reportDirto$(System.DefaultWorkingDirectory)and attempts to publish an existing report.Regression
The same pipeline previously completed successfully with Allure Report extension version
2.2.3.No intentional changes were made to the
PublishAllureReport@2configuration other than temporarily addingreportDir: ''to verify whether an explicit empty value would prevent existing-report mode.All reactions