action #109623
closedcoordination #91646: [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release
coordination #109641: [epic] qem-bot improvements
Allow adding scheduling settings for informal purposes that are not added to openQA jobs
0%
Description
Motivation¶
See #108944#note-4
to not overcrowd job details setting pages we should invent a special prefix which only applies to schedule variables, like we already use _OBSOLETE and _ONLY_OBSOLETE_SAME_BUILD and do not forward such variables to the job.
This could even help us to streamline variables used by our tooling but not directly by test.
Acceptance criteria¶
- AC1: specially-prefixed variables are visible in the scheduled product settings but not added as job settings
Suggestions¶
- __...
- OPENQA_SCHEDULE...
- OPENQA_COMMENT...
Updated by okurz over 1 year ago
- Status changed from New to In Progress
Created a new ticket and deleted the old as that one caused problems with the redmine installation.
Updated by okurz over 1 year ago
Updated by okurz over 1 year ago
- Related to coordination #109641: [epic] qem-bot improvements added
Updated by okurz over 1 year ago
Updated by okurz over 1 year ago
- Related to action #108944: 5 whys follow-up to Missing (re-)schedules of SLE maintenance tests size:M added
Updated by okurz over 1 year ago
- Description updated (diff)
For more context from #108944#note-4:
Why is it so hard to find out starting from an openQA job details page why that job was created [in particular for QA maintenance related jobs]?
- Scheduling settings don't contain an URL to e.g. some GitLab pipeline that did the scheduling. -> helpful in general but in the specific case we were encountering "missing jobs" rather than "wrongly scheduled jobs"
- -> When scheduling openQA tests from bot-ng add two more settings, the URL pointing to a certain incident as shown on the dashboard, e.g. https://dashboard.qam.suse.de/incident/23309 . And as second setting the gitlab CI job URL that triggered
- -> make URL clickable on https://openqa.suse.de/admin/productlog?id=887145 same as for the job settings page
So the point "make URL clickable" is addressed by https://github.com/os-autoinst/openQA/pull/4592/commits/a4bb44fd3397c89c3ffd6465062a45c04cb0726e as part of https://github.com/os-autoinst/openQA/pull/4592 . Will you also look into "When scheduling openQA tests from bot-ng add two more settings"? I guess you could add both settings near https://github.com/openSUSE/qem-bot/blob/7a3bd4d9dde1a6246d404d0b716a5af320d0162b/openqabot/types/incidents.py#L105= as well as https://github.com/openSUSE/qem-bot/blob/e4e831e242ea47d96254616bdc3a1009db41ee09/openqabot/types/aggregate.py#L154= , at best of course without duplicating.
Updated by mkittler over 1 year ago
- Status changed from In Progress to Feedback
Ah, you replaced the original ticket. So it wasn't just me who couldn't edit it anymore. The PR has been merged.
Updated by mkittler over 1 year ago
The URL displaying already works on OSD: https://openqa.suse.de/admin/productlog?id=894293
Updated by okurz over 1 year ago
- Status changed from Feedback to Resolved
Looks good on OSD now, see #109512#note-8