Actions
action #110409
closedcoordination #91646: [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release
coordination #109641: [epic] qem-bot improvements
qem-dashboard - remove old openQA jobs when rr_number changes size:M
Start date:
2022-04-28
Due date:
% Done:
0%
Estimated time:
Description
Motivation¶
#109310 was a good start, but not quite enough to resolve https://github.com/openSUSE/qem-dashboard/issues/61. Incidents might be reused from one day to the next, so only deleting data that is 90 days old does not cover such cases.
Acceptance criteria¶
- AC1: Whenever the
rr_numberof an incident changes, delete existing openQA jobs in the database. - AC2: Ensure that there are no performance regressions
Suggestions¶
- Trigger the rr_number check from the same API that does the 90 day cleanup.
Updated by kraih over 2 years ago
- Related to action #109310: qem-bot/dashboard - mixed old and new incidents size:M added
Updated by okurz over 2 years ago
- Subject changed from qem-dashboard - remove old openQA jobs when rr_number changes to qem-dashboard - remove old openQA jobs when rr_number changes size:M
- Target version changed from future to Ready
Updated by openqa_review over 2 years ago
- Due date set to 2022-05-17
Setting due date based on mean cycle time of SUSE QE Tools
Updated by kraih over 2 years ago
Updated by kraih over 2 years ago
Added a log message to make this easier to verify: https://github.com/openSUSE/qem-dashboard/commit/46a110e2fa205b289f59e89fc4f71050b4123ae4
Updated by kraih over 2 years ago
- Status changed from Feedback to Resolved
The feature is being used in production:
May 17 10:14:15 qam2 dashboard[20256]: [20256] [i] Cleaning up old jobs for incident 24247, rr_number change: 272218 -> 272456
Considering there are no complaints yet, we can probably assume it works.
Updated by jbaier_cz over 2 years ago
- Related to action #114694: Incident seems to have missing aggregate test results in qem-dashboard but openQA jobs exists size:M added
Actions