We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paste the output here
Windows 10
Jenkins pipeline step
allure includeProperties: true, jdk: '', properties: [[key: "reportName", value: "Tests Results"]], results: [[path: "${resPath}"]]
Report name should be "Test Results" instead of the default "Allure Report"
Doesn't change default report name "Allure Report"
I also tried to add a executor.json file that contains a reportName key and value "Test Results"
now if i serve the allure results locally with: allure serve ${resPath} the served local report has a changed report name
allure serve ${resPath}
But if i add the same exutor.json to the jenkins pipeline the jenkins allure report name will not be affected.
There should be a way to define a custom report name even when the report is being served by Jenkins.
Sure
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Windows 10
Reproduction steps
Jenkins pipeline step
Expected Results
Report name should be "Test Results" instead of the default "Allure Report"
Actual Results
Doesn't change default report name "Allure Report"
Anything else?
I also tried to add a executor.json file that contains a reportName key and value "Test Results"
now if i serve the allure results locally with:
allure serve ${resPath}
the served local report has a changed report nameBut if i add the same exutor.json to the jenkins pipeline the jenkins allure report name will not be affected.
There should be a way to define a custom report name even when the report is being served by Jenkins.
Are you interested in contributing a fix?
Sure
The text was updated successfully, but these errors were encountered: