Project

General

Profile

Actions
Copy link

action #101457

open

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

Added by rpalethorpe over 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
QA - future
Start date:
2021-10-25
Due date:
% Done:

0%

Estimated time:
Tags:
openQA

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

Actions
Copy link
 #1

Updated by rpalethorpe over 2 years ago

  • Tracker changed from coordination to action
Actions
Copy link
 #3

Updated by okurz over 2 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

Actions
Copy link
 #4

Updated by okurz almost 2 years ago

  • Parent task changed from #91914 to #99306
Actions
Copy link

Also available in: Atom PDF