Skip to content

build-dm-verity-task: make the labels a parameter to the task#174

Open
littlejawa wants to merge 1 commit intoconfidential-devhub:mainfrom
littlejawa:make_labels_a_parameter_to_the_task
Open

build-dm-verity-task: make the labels a parameter to the task#174
littlejawa wants to merge 1 commit intoconfidential-devhub:mainfrom
littlejawa:make_labels_a_parameter_to_the_task

Conversation

@littlejawa
Copy link
Copy Markdown
Collaborator

@littlejawa littlejawa commented Mar 9, 2026

The task currently has hardcoded labels that it applies to the image. Part of them contain the release version in it, forcing us to modify/rebuild the task every time we make a new release. It also means that a given task cannot be used for different releases.

This commit moves the list of labels to a parameter to the task, and modify the build script to loop on that list and apply them one by one. It also modifies the dm-verity build pipelines to provide this list as intended.

Similar changes are applied to the debug flavor of the build task and pipelines, for consistency.

@littlejawa littlejawa marked this pull request as draft March 9, 2026 10:22
@littlejawa
Copy link
Copy Markdown
Collaborator Author

/cc @snir911 @dbkreling

This should help in the general case (making a new release should not involve modifying the build task).
Making the task more generic also means that we could, in theory, use the same task for different versions of OSC.
See my comment in #171 - the 1.11 branch should be able to use the same task, except for this version string.

Keeping it as a draft for now, I want to double-check the resulting image.

@littlejawa littlejawa force-pushed the make_labels_a_parameter_to_the_task branch 3 times, most recently from ecfb010 to 5d6a96f Compare March 9, 2026 17:40
@littlejawa
Copy link
Copy Markdown
Collaborator Author

/retest

The task currently has hardcoded labels that it applies to the image.
Part of them contain the release version in it, forcing us to modify/rebuild
the task every time we make a new release. It also means that a given task
cannot be used for different releases.

This commit moves the list of labels to a parameter to the task, and modify
the build script to loop on that list and apply them one by one.
It also modifies the dm-verity build pipelines to provide this list as intended.

Similar changes are applied to the debug flavor of the build task and pipelines,
for consistency.

Signed-off-by: Julien Ropé <jrope@redhat.com>
@littlejawa littlejawa force-pushed the make_labels_a_parameter_to_the_task branch from bf37a29 to f670966 Compare March 10, 2026 14:37
@littlejawa littlejawa marked this pull request as ready for review March 10, 2026 14:38
@littlejawa
Copy link
Copy Markdown
Collaborator Author

Verified using the "debug" image generated with this PR (the "normal" version is still using the previous build task).
After a couple fixups, I managed to make an image where the labels are 100% identical to the previous build.

@littlejawa
Copy link
Copy Markdown
Collaborator Author

/retest

1 similar comment
@littlejawa
Copy link
Copy Markdown
Collaborator Author

/retest

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.

1 participant