Project

General

Profile

Actions

action #97580

closed

QA (public) - coordination #69310: [epic] SUSE QA tools team ticket process helpers

Automatic check for qa-tools backlog limits in Github Actions

Added by VANASTASIADIS over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2021-08-27
Due date:
% Done:

0%

Estimated time:

Description

User story

Instead of manually accessing the custom queries defined in https://progress.opensuse.org/projects/qa/wiki/#Target-numbers-or-guideline-should-be-in-priorities, it would be nice to have automatic checks for those in a gh actions workflow.

Acceptance criteria

  • AC1: A scheduled Github Actions workflow exists that fails when the target numbers for any one of the defined queries are not met
  • AC2: Consider if any further action would be desired (like an alert in case of target numbers not being met)

Tasks

Further details

A POC exists here: https://github.com/BillAnastasiadis/qa-tools-backlog-assistant/actions

Actions #1

Updated by VANASTASIADIS over 3 years ago

  • Parent task set to #69310
Actions #2

Updated by VANASTASIADIS over 3 years ago

  • Status changed from New to Feedback
  • Target version changed from future to Ready
Actions #3

Updated by VANASTASIADIS over 3 years ago

  • Status changed from Feedback to Resolved

Feature is working as expected in https://github.com/os-autoinst/qa-tools-backlog-assistant. Resolving the ticket.

Actions #4

Updated by okurz over 3 years ago

  • Status changed from Resolved to Feedback
  • Assignee set to VANASTASIADIS

Does the action fail if one of the alerts trigger?

Actions #5

Updated by VANASTASIADIS over 3 years ago

Good question: The action does fail if any of the alerts trigger, but not before running all of the checks first - so that if more than one queries fail, they are all shown and not only the first one.

Actions #6

Updated by VANASTASIADIS about 3 years ago

  • Status changed from Feedback to Resolved

I think it's safe to say that this ticket is now resolved. Further fixes and improvements can be discussed in https://progress.opensuse.org/issues/98186.

Actions

Also available in: Atom PDF