-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
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
Naming reports #142
Comments
@eilonreifs I could handle an option to do that. I will put it in the backlog. Thanks |
Hi @eilonreifs Regarding your requirement. When you say this: I think if you want to keep the report permanently, maybe we need to create another place to store that report, something like |
Hi @fescobar , I am aware of the limit. |
@eilonreifs Ok, let me think about that. Thanks |
It could also be useful to use snapshot names, instead of id or date as well |
Is it possible to make the report name completely controllable? Does it make sense the presence of an index before |
@adamakalshchikov it's not possible to do that. It seems to be an easy change, but with that, I will lose complete control of the reports. Always I need the index. |
+1 for this feature, we are using custom name in format <SERVICE_NAME>_<DATETIME_OF_TESTING> for our reports so even with index digits in front it would be much easier to find required report than just by number. |
any update regarding of it? would like to bind it to a build id, it is an increasing integer so there is no way of losing control of the reports |
Hi @fescobar, +1 for this feature.
UPD: After checking out keepAllureLatestHistory.sh) I understood why not having the ID is so inconvenient =) but I guess it's still doable. |
Hi,
It could be awesome if you will add an option of naming the report when creating it through the API, instead of just giving it arbitrary names (e.g. 1,2,3).
It can be very useful for the purpose of preserving the reports for the long term.
Thanks!
The text was updated successfully, but these errors were encountered: