search

allure-framework / allure-teamcity

Teamcity CI plugin allowing to generate Allure Report as build artifact
https://qameta.io/allure-report
Apache License 2.0
37 stars 29 forks source link

Parameter for report artifact subdirectory is ignored #65

Closed KillAChicken closed 6 years ago

KillAChicken commented 6 years ago

I'm submitting a ...

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Add a build step for allure report and specify allure_report as a report artifact subdirectory. New report is generated, but the artifacts are published to the root directory.

What is the expected behavior?

The artifacts are published to the directory allure_report.

What is the motivation / use case for changing the behavior?

Issue is related to https://github.com/allure-framework/allure-teamcity/pull/37 and https://github.com/allure-framework/allure-teamcity/issues/34

Please tell us about your environment:

allure-teamcity@2.6

Other information

It seems that the proper behavior could be implemented by specifying user input explicitly in the method afterProcessSuccessfullyFinished of the class AllureBuildServiceAdapter As far as I understand, something like artifactsWatcher.addNewArtifactsPath(reportDirectory.toString() + " => " + getRunnerParameters().get(REPORT_PATH_PREFIX)); should do the trick.

alexKazarin commented 6 years ago

Same problem. Allure-teamcity: 2.6 Allure-commandline: 2.4.1