action #109623: Allow adding scheduling settings for informal purposes that are not added to openQA jobs - QA - openSUSE Project Management Tool

Custom queries

may-sprint
new immediate tickets
openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QE tools team - backlog (ready issues)
QE tools team - backlog (w/o infra)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - triage: untriaged issues
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #109623

closed

coordination #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

Added by okurz about 2 years ago. Updated about 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

mkittler

Target version:

openQA Project - Ready

Start date:

2022-03-24

Due date:

% Done:

Estimated time:

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...

Related issues 1 (0 open — 1 closed)

Related to QA - action #108944: 5 whys follow-up to Missing (re-)schedules of SLE maintenance tests size:M

Resolved

osukup

2022-03-24

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by okurz about 2 years ago

Description updated (diff)

Actions

Copy link

Updated by okurz about 2 years 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.

Actions

Copy link

Updated by okurz about 2 years ago

https://github.com/os-autoinst/openQA/pull/4592

Actions

Copy link

Updated by okurz about 2 years ago

Related to coordination #109641: [epic] qem-bot improvements added

Actions

Copy link

Updated by okurz about 2 years ago

Parent task set to #109641

Actions

Copy link

Updated by okurz about 2 years ago

https://github.com/os-autoinst/openQA/pull/4592 merged

Actions

Copy link

Updated by okurz about 2 years ago

Related to action #108944: 5 whys follow-up to Missing (re-)schedules of SLE maintenance tests size:M added

Actions

Copy link

Updated by okurz about 2 years 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.

Actions

Copy link

#10