-
Notifications
You must be signed in to change notification settings - Fork 184
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
Incorrect project build number used in certain scenario #141
Comments
Hi @apulverizer when you move your directories do it keeping timestamps Something like this: mv --recursive --preserve=timestamps [SOURCE] [DESTINY] |
@fescobar thanks, if we move the directories again we'll do that. We made an assumption that the max build number was fetched and then incremented so it didn't occur to us that it was based on the modified time. |
@apulverizer I will add documentation about that. |
I also encounter the same issue. I try to store report outputs on S3 and sync it to a volatile docker container to generate a new reports version. The issue is that Amazon S3 doesn't preserve modification times and all times are set to the time when I upload previous results to S3. A simple change with sorting would solve the issue:
|
Hi @fescobar
We've run into a problem where when calling the generateReport endpoint, it's storing the results in an older build directory instead of incrementing by 1. For example say we have a reports directory in a project of:
We'd expect the next report to be stored in
111
. However it is being stored in109
, for example.What happened is that we changed the directory where we were storing projects and moved it to a new location. When those directories and report files were moved, it altered the last modified time of the directories.
So then when this is called:
allure-docker-service/allure-docker-scripts/generateAllureReport.sh
Line 15 in 351f028
It is not returning
110
but is returning108
which then gets incremented to109
.Is it possible to actually sort the numeric reports instead of relying on the last modified time?
It seems like a workaround for us is to
touch
the most recent directory within each project.The text was updated successfully, but these errors were encountered: