Project

General

Profile

Actions

coordination #154780

closed

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

[epic] openQA scenario definitions fully in git

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

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

100%

Estimated time:
(Total: 0.00 h)

Description

Further ideas

only for the kernel squad but we learn from it and might take over some ideas

  • Fix issues in the kernel yaml schedule repo documentation if any -> report ticket to kernel squad

for all other SUSE QE squads

  • Conversion script to be usable (in theory) for os-autoinst-distri-opensuse -> proof of concept exists, we shouldn't plan to continue for now

for QE tools

  • Add a version to the existing scenario definitions (so that we can introduce breaking changes in a subsequent version) -> we should only do that if we implement any specific breaking feature

  • Help with better reusing bigger schedule definitions: Add a defaults for scenario definitions with settings, like in https://gitlab.suse.de/tinita/kernelqa-openqa-yaml/-/commit/4fdd7ff6b61cb7343202f1bf0f73c5953f1a6cb9#9e43e18bae06f0c8e143b0b63b2ab2fdfd4b2013_0_6

  • Add support for re-using testsuites from another file -> for this we want to be explicit which scenarios inherit from test suites and which don't, hence our proposal:

    • =openqa_from_bootstrap: # our proposal for looking up existing testsuites
  • Decide on a good format based on tinita's script proposal

  • Add the extension ideas from #155218-22 into the existing scenario definitions implementation, e.g.

    • =(openqa_from_bootstrap)_but_different: # proposal for testsuite look-up with custom name for job template with additional settings
  • Support other ideas from #155218 from tinita, e.g.

    • specifying the architecture e.g. with an @
    • the architecture in prod-ver-flavor-arch1 is duplicated because it's already under a arch1 key

Subtasks 5 (0 open5 closed)

action #132335: In openqa-in-openqa use scenario definitions instead of job group templates size:MResolvedosukup2023-06-01

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

Actions
action #157774: Empty scenario definitions causing Use of uninitialized value $testsuite_name in hash element in lib/OpenQA/Schema/Result/JobGroups.pm size:SResolvedlivdywan2024-03-22

Actions
action #160206: Minimum working example for job templates YAML import/include/inherit in kernelqa-openqa-yaml size:SResolvedtinita

Actions
action #160209: Reduce duplication in machine definitions in https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/scenario-definitions.yaml#L8, e.g. with re-usable machine "defaults" size:SResolveddheidler

Actions

Related issues 1 (1 open0 closed)

Copied to openQA Project - coordination #162545: [epic] Further ideas for openQA scenario definitions fully in gitNew

Actions
Actions #1

Updated by okurz 5 months ago

  • Subtask #132335 added
Actions #2

Updated by okurz 4 months ago

  • Subtask #155218 added
Actions #3

Updated by okurz 3 months ago

  • Status changed from New to Blocked
  • Assignee set to okurz
Actions #4

Updated by okurz 3 months ago

  • Subtask #157774 added
Actions #5

Updated by okurz about 1 month ago

  • Subtask #160206 added
Actions #6

Updated by okurz about 1 month ago

  • Subtask #160209 added
Actions #7

Updated by okurz about 1 month ago

  • Description updated (diff)

Incorporated ideas from consolidation session with tinita, livdywan, okurz

Actions #8

Updated by okurz about 1 month ago

  • Description updated (diff)
Actions #9

Updated by okurz 2 days ago

  • Copied to coordination #162545: [epic] Further ideas for openQA scenario definitions fully in git added
Actions #10

Updated by okurz 2 days ago

  • Status changed from Blocked to Resolved
  • Target version changed from Tools - Next to Ready

Follow-up defined and put into separate ticket

Actions

Also available in: Atom PDF