Change gz-collections.yaml spec to support ci configs #970
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The PR should not change any existing code but reforms the yaml spec to define how the libs and ci interacts:
ci_configs
section that can host all related CI details and the different collections only reference them by name. Names are equal to Ubuntu distributions but could be something different.generate_ciconfigs_by_lib
is a parse step that builds an index of ci-configurations supported by each lib. It should help to avoid extra parsing in the diffferent jobs creation.generate_label_by_requirements
handles the label selection for the jobs, nvidia or large-memory.I would not expect any XML code change with the exception of gz-harmonic repo removal since now we are excluding it.