mirror of
https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git
synced 2025-07-13 09:01:34 +00:00
f966128089
I've always hated the magic group name derivation in fifloader, and it prevents it being used by anyone but Fedora. This fixes that by requiring group_name to be set in the Products. This is an executive decision, but it makes sense at least with how Fedora uses openQA. If other users who might want to adopt fifloader *don't* have a 100% assocation from products to job groups, we can introduce more ways to set it in future, I guess. I made it compulsory because it feels weird to have job templates that aren't in groups...I don't even know how those get shown in the web UI. But if there's a real use case for this we can make it optional. Signed-off-by: Adam Williamson <awilliam@redhat.com> |
||
|---|---|---|
| .. | ||
| fif-arch.json | ||
| fif-complete.json | ||
| fif-distri.json | ||
| fif-flavor.json | ||
| fif-flavors.json | ||
| fif-incomplete.json | ||
| fif-machine.json | ||
| fif-machines.json | ||
| fif-predefault.json | ||
| fif-product-predefault.json | ||
| fif-product.json | ||
| fif-productdefaults.json | ||
| fif-products-predefault.json | ||
| fif-products.json | ||
| fif-profile.json | ||
| fif-profilegroup.json | ||
| fif-profilegroups.json | ||
| fif-profiles.json | ||
| fif-settingshash.json | ||
| fif-testsuite.json | ||
| fif-testsuites.json | ||
| fif-version.json | ||
| openqa-complete.json | ||
| openqa-incomplete.json | ||
| openqa-jobgroup.json | ||
| openqa-jobgroups.json | ||
| openqa-jobtemplate.json | ||
| openqa-jobtemplates.json | ||
| openqa-machine.json | ||
| openqa-machines.json | ||
| openqa-product.json | ||
| openqa-products.json | ||
| openqa-settingsarray.json | ||
| openqa-testsuite.json | ||
| openqa-testsuites.json | ||
| README.md | ||
FIF and openQA template schemas
This directory contains JSON Schema format schemas for the FIF and
upstream openQA template data formats. fif-complete.json and fif-incomplete.json are the FIF
schemas; openqa-complete.json and openqa-incomplete.json are the upstream schemas. The
'complete' schemas expect the input to contain a complete set of template data (enough for an
openQA instance to schedule and run tests); the incomplete schemas expect the input to contain
only some valid template data (these may be files that will be combined into complete data, or
files intended to be loaded without --clean only as supplementary data to an openQA deployment
with existing data). The other files are subcomponents of the schemas that are loaded by reference.