Repository navigation
ose-osc: add dm-verity build task for s390x as a trusted task - #309
Open
littlejawa wants to merge 1 commit into
Open
littlejawa wants to merge 1 commit into
littlejawa wants to merge 1 commit into
Conversation
Our partners at IBM have duplicated our build process for dm-verity, making a dedicated pipeline creating an image for s390x. The build processes being very different, we want to keep them separated, and have a dedicated build task for that. But then, we need to make this task trusted to allow releasing the resulting image. Signed-off-by: Julien Ropé <jrope@redhat.com>
littlejawa
requested review from
bhills-rh,
jnkubica,
rhartman93 and
semccart-rh
as code owners
November 12, 2026 09:09
Author
|
@rhartman93 @simonbaird - you've been working with us on dm-verity in the past. Can you help here? |
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
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.
Our partners at IBM have duplicated our build process for dm-verity, making a dedicated pipeline creating an image for s390x.
The build processes being very different, we want to keep them separated, and have a dedicated build task for that. But then, we need to make this task trusted to allow releasing the resulting image.
NOTE: I understand that #294 is changing the location of this rules, but we will need it trusted pretty soon. I can move it if needed, but I'd rather have it visible here for discussion first.
Fixes: https://redhat.atlassian.net/browse/KATA-6376