action #101457
openQA (public) - coordination #99303: [saga][epic] Future improvements for SUSE Maintenance QA workflows with fully automated testing, approval and release
coordination #99306: [epic] Future improvements: Make reviewing openQA results per squad easier
Native per-module bug tags
0%
Description
Motivation¶
We need to tag individual modules (e.g. LTP tests) within a job. Presently we (kernel qa) do this within job comments using syntax like "test123: bug#123". This requires parsing job comments.
Other teams have different solutions, like parsing external YAML files and marking individual modules as soft-failed.
Providing a single structured data source in OpenQA will simplify reporting and bug tag propagation.
Goal¶
Provide simple interface through OpenQA to:
- assign a bug to a job module
- query the bug assigned to a job module
- remove a bug from a job module
I think a single reference to one bug tracker is sufficient. Related items in other trackers can be handled by one external tracker (e.g. Redmine).
Non-Goals¶
- Propagate bugs from one build to the next
- Notifications or reporting
Alternatives¶
- External service and database (e.g https://gitlab.suse.de/kernel-qa/bugtags)
Updated by rpalethorpe about 3 years ago
- Tracker changed from coordination to action
Updated by okurz about 3 years ago
- Priority changed from Normal to Low
- Target version set to future
Good idea. As we already do a carry over based on modules we could look into extending that