metadata: add EXTRA_METADATA for job metadata keys - #98
Merged
Milosz Wasilewski (mwasilew) merged 1 commit intoSep 9, 2026
Merged
Conversation
Recording anything new in the LAVA job metadata meant adding a variable to every project template first. Accept a mapping instead: every key in EXTRA_METADATA is added to the metadata of the rendered job, so callers can record build details without a change here. Project templates now name their keys in a METADATA dict and share one renderer. A key that collides with a named one is dropped rather than emitted twice, which would fail the job. Mappings are merged across variables files instead of replacing each other. Signed-off-by: Matt Hart <matthart@qti.qualcomm.com>
Milosz Wasilewski (mwasilew)
approved these changes
Sep 9, 2026
Milosz Wasilewski (mwasilew)
merged commit Sep 9, 2026
2f2900c
into
qualcomm-linux:master
5 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Recording anything new in the LAVA job metadata meant adding a variable to every project template first. Accept a mapping instead: every key in EXTRA_METADATA is added to the metadata of the rendered job, so callers can record build details without a change here.
Project templates now name their keys in a METADATA dict and share one renderer. A key that collides with a named one is dropped rather than emitted twice, which would fail the job. Mappings are merged across variables files instead of replacing each other.