search

jenkinsci / allure-plugin

Allure Jenkins Plugin
https://plugins.jenkins.io/allure-jenkins-plugin/
Other
84 stars 63 forks source link

variables in results path don't work #280

Open roydekleijn opened 3 years ago

roydekleijn commented 3 years ago

does this need to be addressed here as well?

https://github.com/jenkinsci/allure-plugin/issues/219

Issue Context Jenkins version: 2.141 Job type: Freestyle Allure plugin version: 2.27.0 Allure commandline version: 2.6.0

Problem description Using a variable in results path causes build to fail:

set Report path to "report/$BUILD_NUMBER/allure-report" the build will fail with NoSuchFileException, but the path indeed contains allure results removing variable from results-path resolves the issue If we take a look in the logs, we'll see that the variable is not substituted with the value. The main reason to use variables in results path is to isolate results from each other so that report will not be accumulated with each build.

Logs & Traces 11:22:22 [bqc] $ "D:\Program Data\Jenkins\workspace\tools\ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation\allurecommand\bin\allure.bat" generate "D:\Program Data\Jenkins\workspace\bqc\Report\132\allure-results" -c -o "D:\Program Data\Jenkins\workspace\bqc\report\$BUILD_NUMBER\allure-report" 11:22:36 Report successfully generated to D:\Program Data\Jenkins\workspace\bqc\report\132\allure-report 11:22:36 Allure report was successfully generated. 11:22:36 Creating artifact for the build.

tavisca-amitesh commented 3 years ago

Is there any update on this issue?