Actions
action #114451
closedIncidents from all test issues variables are collected during bisect size:M
Description
Observation¶
https://openqa.suse.de/tests/9184859#comments shows a comment from openqa-investigate. As this job is an aggregate test I would have expected also a result from https://github.com/os-autoinst/scripts/blob/master/openqa-trigger-bisect-jobs but we only have one entry in the job setting OS_TEST_ISSUES. Likely we should also trigger based on entries in BASE_TEST_ISSUES, DESKTOP_TEST_ISSUES, etc.
Acceptance criteria¶
- AC1: Results from openqa-trigger-bisect-jobs are shown in job comments whenever an aggregate test includes entries in multiple TEST_ISSUES variables
- AC2: Incidents are pulled from all *_TEST_ISSUES variables
Suggestions¶
- Understand the meaning of the different "TEST_ISSUES" variables We don't care, we just assume we can treat all the same
- Extend https://github.com/os-autoinst/scripts/blob/master/openqa-trigger-bisect-jobs to look into multiple TEST_ISSUES variables instead of just OS_TEST_ISSUES
Out of scope¶
- Do not care about performance impact of "too many openQA jobs" triggered, we should have enough capacity
Actions