Skip to content

tests/validate_yaml: add validation for KCIDB mapping - #643

Merged
nuclearcat merged 1 commit into
kernelci:mainfrom
JenySadadia:validate-kcidb-mapping
Jun 14, 2024
Merged

nuclearcat merged 1 commit into
kernelci:mainfrom
JenySadadia:validate-kcidb-mapping

Conversation

@JenySadadia

Copy link
Copy Markdown
Contributor

To submit KernelCI generated data to KCIDB, it is required to have a mapping for all the job definitions with
kcidb_test_suite property.
Add validation to ensure all the jobs have a mapping present to avoid missing data submission. This check is to notify test authors trying to enable tests in maestro to include the required property for the mapping in their definition.

To submit KernelCI generated data to KCIDB, it is required
to have a mapping for all the job definition with
`kcidb_test_suite` property.
Add validation to ensure all the jobs have a mapping
present to avoid missing data submission.
This check is to notify test authors trying to enable tests
in maestro to include the required property for the mapping
in their definition.

Signed-off-by: Jeny Sadadia <jeny.sadadia@collabora.com>

@pawiecz pawiecz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

These checks could also be added to kci config validate tool (which checks section order) but that's a future task

@nuclearcat

Copy link
Copy Markdown
Member

I think it is good if i merge it asap, so it will validate current config updates. Thank you!

@nuclearcat
nuclearcat added this pull request to the merge queue Jun 14, 2024
Merged via the queue into kernelci:main with commit ab270ed Jun 14, 2024
@JenySadadia
JenySadadia deleted the validate-kcidb-mapping branch June 14, 2024 11:07
@JenySadadia

Copy link
Copy Markdown
Contributor Author

LGTM

These checks could also be added to kci config validate tool (which checks section order) but that's a future task

Yes, that's a good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants