Actions
action #182666
openQA (public) - coordination #99303: [saga][epic] Improvements for SUSE Maintenance QA workflows with fully automated testing, approval and release
coordination #99306: [epic] Improvements: Make reviewing openQA results per squad easier
[research][timeboxed:6h] Find out what is the best approach to store and lookup openQA job metadata from our database, e.g. indexed job settings, "job_tags" table, only one value per key
Start date:
Due date:
% Done:
0%
Estimated time:
Description
Motivation¶
From #121246-15: "We'd need to look for all the tests that are failing for a given incident, using the same TEST_ISSUES for both, Aggregates and Incidents". After #117655 we identified that we can use that to filter but there is a key/job id limit so we need to find out how to work with a much larger limit e.g. with a database index.
Goals¶
- G1: We know current state of art of handling such data efficiently in PostgreSQL
Suggestions¶
- Understand the current performance implications in particular related to comma-separated values in openQA job settings, e.g. "OS_TEST_ISSUES=42431,42432"
- Conduct a web research, ask colleagues, AI. Try out solutions yourself
Updated by okurz about 12 hours ago
- Copied from action #156547: A single API route to show all tests related to a SLE maintenance incident size:M added
Updated by okurz about 12 hours ago
- Copied to action #182669: [spike][timeboxed:10h] Benchmark advanced indexing and trigram gin index for /job_settings API added
Actions