action #54179

openQA Tests - coordination #15132: [saga][epic] Better structure of test plans in

coordination #44360: [epic] Parameterize test suites within job groups

Re-use YAML betweens different groups

Added by cdywan almost 3 years ago. Updated over 1 year ago.

Feature requests
Target version:
Start date:
Due date:
% Done:


Estimated time:


A feature request has been suggested as part of the testing of the YAML editor on staging.

Alias can be used to simplify YAML for a job group, and reduce duplication. But it can't currently be shared across multiple groups.

YAML::PP::LibYAML supports the !include feature, however according to tinita it currently expects files on disk. We would need a way to include snippets from the database.


#1 Updated by tinita almost 3 years ago

I will try to figure out an addition to the !include API that allows to load from database or other places.

#2 Updated by cdywan almost 3 years ago

QAM could reuse aliases between YAMLs within Update|Incidents groups e.g. there are subgroups which could use YAML alias of tests running on all versions, another alias running only on sle15 and so on.

But that sounds like a layer above this. I.e. maintain your input in a git repository, expand the yaml to your linking and post it to the API for all groups. But expecting the UI to support aliases and includes is not what I think we should do.

Preprocessing sounds like a very interesting option as well.

Note this proposal is a long term thing. So if more people ask about it we have a ticket to refer to, and we can estimate the work for when we decide if we want something like that.
A wishlist item really, but I couldn't find a label for that in progress.

#3 Updated by okurz almost 3 years ago

  • Target version set to future

the "future" target version is our wishlist as in "would be nice … but not now" :)

#4 Updated by okurz almost 3 years ago

  • Related to action #49535: Improve time to schedule a build added

#5 Updated by okurz almost 3 years ago

  • Related to deleted (action #49535: Improve time to schedule a build)

#6 Updated by okurz over 1 year ago

  • Priority changed from Normal to Low

Also available in: Atom PDF