You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Existing logic: keep_reports action is default to 20, after the reports count over than 20, it will remove the last history, and we treat the smallest build number folder as the last history
But we have a scenario that the smallest build number is not the real last history.
Condition:
The repo only has one project, so it's not the case which subfolder mentioned.
We created 2 actions one is for running job by push, another is for schedule. Each has their own build number like above screenshot
Issue:
In my case, the on schedule build number #6 is the newly generated, but when next push happens, the #6 allure history report was removed as the total report count over than 20. This caused me can't access the #6 generated report anymore. May I seek for your help on how to handle my scenario?
The text was updated successfully, but these errors were encountered:
Existing logic:
keep_reports action is default to 20, after the reports count over than 20, it will remove the last history, and we treat the smallest build number folder as the last history
But we have a scenario that the smallest build number is not the real last history.
Condition:
Issue:
In my case, the on schedule build number #6 is the newly generated, but when next push happens, the #6 allure history report was removed as the total report count over than 20. This caused me can't access the #6 generated report anymore. May I seek for your help on how to handle my scenario?
The text was updated successfully, but these errors were encountered: