Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

AllureBamboo plugin uses all the artifacts generated by a build #40

Closed
smecsia opened this issue Nov 15, 2017 · 1 comment
Closed

AllureBamboo plugin uses all the artifacts generated by a build #40

smecsia opened this issue Nov 15, 2017 · 1 comment

Comments

@smecsia
Copy link
Contributor

smecsia commented Nov 15, 2017

If you have several types of artifacts produced by a build, e.g. allure-results and surefire-reports, Allure Bamboo tries to generate the report out of all of them. This might be not a good idea.

Also it does not respect files with the same names in the artifacts provided by different jobs, i.e. if your jobs generate surefire reports for the same test classes, some of the results would be lost.
smecsia added a commit to smecsia/allure-bamboo that referenced this issue Nov 22, 2017
@smecsia
Allow artifacts to have same names on different stages (refs allure-f…
3a9ac5c 
…ramework#40)
smecsia added a commit that referenced this issue Dec 5, 2017
@smecsia
Allow artifacts to have same names on different stages (refs #40) (#41)
5b72f8a 
* Allow artifacts to have same names on different stages (refs #40)

* Deprecate Allure Report task
@smecsia
Copy link
Contributor Author

smecsia commented Feb 13, 2018

Fixed via #44

@smecsia smecsia closed this as completed Feb 13, 2018
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@smecsia