Project

General

Profile

Actions

action #160206

closed

coordination #58184: [saga][epic][use case] full version control awareness within openQA

coordination #154780: [epic] openQA scenario definitions fully in git

Minimum working example for job templates YAML import/include/inherit in kernelqa-openqa-yaml size:S

Added by okurz 2 months ago. Updated 28 days ago.

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

0%

Estimated time:

Description

Motivation

What we learned in #155218 and we want to define a good structure for cross-file re-use of scenario definitions. For this we want to take inspiration from the kernelqa-openqa-yaml approach.

Acceptance criteria

  • AC1: Minimum working example for job templates YAML import/include/inherit exists in kernelqa-openqa-yaml

Suggestions

  • Continue what tinita started in #155218 coming up with a unit test that would make up a minimum example, because manual examples get outdated -> Add tests for kernel schedule repo

Related issues 1 (0 open1 closed)

Copied from openQA Project - action #155218: [spike][timeboxed:30h] Use scenario definitions instead of job group templates for os-autoinst-distri-opensuse size:MResolvedtinita

Actions
Actions #1

Updated by okurz 2 months ago

  • Copied from action #155218: [spike][timeboxed:30h] Use scenario definitions instead of job group templates for os-autoinst-distri-opensuse size:M added
Actions #2

Updated by openqa_review 2 months ago

  • Due date set to 2024-05-25

Setting due date based on mean cycle time of SUSE QE Tools

Actions #4

Updated by tinita 2 months ago

  • Status changed from In Progress to Feedback
Actions #6

Updated by tinita about 2 months ago

  • Status changed from Feedback to Resolved

No response to the other PR.

Actions #7

Updated by okurz 28 days ago

  • Due date deleted (2024-05-25)
Actions

Also available in: Atom PDF