Project

General

Profile

Actions

openqa-force-result #109857

closed

coordination #89062: [epic] Simplify review for SUSE QAM

Secure auto-review+force_result size:M auto_review:"Failed to download gobbledeegoop":force_result:softfailed

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

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Due date:

Description

Motivation

See #104923 . We should only allow a trusted set of people to influence test results on o3+osd using force_result in auto-review tickets.

  • AC1: Only a trusted, known set of people can influence test results on o3+osd using force_result in auto-review tickets

Suggestions

  • Define a new "tracker" in progress.opensuse.org (we already use "action" and "coordination", could add another one there, e.g. "openqa-force-result")
  • Configure "Non member"-permissions to disallow create+update of tickets.
  • Create new sub-project of openqatests using only that tracker (where we trust members, e.g. the "QA" project tree)
  • Extend openqa-label-known-issues to only look into that project for auto-review+force-result (optionally only the specific tracker)

This paired with a progress project where we trust members plus openqa-label-known-issues to only look at a certain tracker for "openqa-force-result" tickets would mean that only members of the specified project can create+update "openqa-force-result" tickets in the "openqa-force-result" tracker.

Rejected alternative: Create a private ticket but this has the significant drawback that soon openQA jobs will be labeled with tickets automatically and not everybody can see the tickets

Actions

Also available in: Atom PDF