Project

General

Profile

coordination #91646

[saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release

Added by okurz 3 months ago. Updated about 22 hours ago.

Status:
Blocked
Priority:
Normal
Assignee:
Target version:
Start date:
2016-02-09
Due date:
2021-07-28
% Done:

42%

Estimated time:
(Total: 0.00 h)

Description

Motivation

Scale up the business while ensuring highest quality with automated testing, approval and release of package updates for SLE and openSUSE


Subtasks

openQA Project - coordination #89062: [epic] Simplify review for SUSE QAMBlockedokurz

openQA Project - action #91542: openQA API what jobs were/are testing X incident/packageResolvedilausuch

openQA Project - action #91658: Make "black certificate" stricter to only show when /tests/overview?todo=1 is empty, i.e. no unlabeled failuresResolvedmkittler

openQA Project - action #91770: Optional job investigation information in "investigation" tab rather than commentsNew

openQA Project - action #91773: Automatic replacement of openQA job URLs preview of openQA New

openQA Infrastructure - action #92034: Re-enable openqa-investigate options after the black certificate now only shows properly "reviewed" jobsResolvedmkittler

action #92851: Workshop series proposal "How SUSE QE teams review openQA test results"Resolvedcdywan

openQA Project - action #93246: List all unreviewed failed (or incomplete) jobs on /tests on requestNew

openQA Project - action #94937: Distinguish comment types on jobs on /tests (maybe optional) size:SResolvedtinita

openQA Project - coordination #91467: [epic] Surface openQA failures per squad in a single placeBlockedokurz

openQA Project - action #91647: Making option to filter by flavor, test name on /tests/overview more prominentResolvedkraih

openQA Project - action #91650: Resolve the most recent builds per job group on /tests/overview when showing multiple job groupsResolvedilausuch

openQA Project - action #91652: Remind about the use of openqa-review in squadsResolvedokurz

openQA Tests - action #92921: [tools][spike] Can we change or display job group structure for maintenance job groups to have one job group per team like for product validation and maybe specific products and versions belowNew

openQA Project - action #92957: Add option to openqa-review to skip displaying all passed resultsResolvedtinita

openQA Project - action #93727: Publish openqa-review reports with "--skip-passed"Resolvedokurz

openQA Project - action #94732: Provide link to /tests/overview of latest builds of all job groups within a parent job group size:MResolvedilausuch

openQA Project - action #94762: openqa-review: Add mode of single-line todo lists size:MResolvedtinita

openQA Project - action #95878: Add filter on /tests/overview for search term in test suite descriptionNew

openQA Project - action #96058: [spike] Filter test results on /tests or /tests/overview by regex match in failed modules size:MWorkable

openQA Project - coordination #91914: [epic] Make reviewing openQA results per squad easierBlockedokurz

openQA Project - action #17252: notifications to maintainer on failed modulesNew

openQA Project - action #91605: notifications about failed and unreviewed jobs - but using Rocket.ChatWorkable

openQA Project - action #92533: Module-centric test result overviewNew

openQA Project - action #92960: Add option to openqa-review to section by flavorWorkable

openQA Project - action #93065: "parallel_failed" jobs show up on /tests/overview?todo=1 but these do not need a labelWorkable

openQA Project - action #95278: Making option to filter by job group(s) on /tests/overview more prominentNew

History

#1 Updated by okurz 3 months ago

  • Project changed from SUSE QA to QA

#3 Updated by okurz 3 months ago

  • Tracker changed from action to coordination

#4 Updated by okurz 3 months ago

  • Subject changed from [saga][epic] Improve SUSE Maintenance QA workflows with fully automated testing, approval and release to [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release

#5 Updated by okurz 3 months ago

  • Target version changed from Ready to future

with #91605 put to future again, see #91605#note-4 , with the support of more internal stakeholders, with the need of focussing on existing sagas to get something done before we pick up more new stories, with the quick solutions applied as part of #91542 and #91467 we decide that currently for the foreseeable future of next weeks we will not continue work here and focus on other sagas instead, see https://progress.opensuse.org/issues?query_id=524

#7 Updated by okurz 26 days ago

  • Target version changed from future to Ready

Also available in: Atom PDF