Skip to content

ose-osc: add dm-verity build task for s390x as a trusted task - #309

Open
littlejawa wants to merge 1 commit into
release-engineering:mainfrom
littlejawa:add-osc-dm-verity-s390x-build-as-trusted-task
Open

littlejawa wants to merge 1 commit into
release-engineering:mainfrom
littlejawa:add-osc-dm-verity-s390x-build-as-trusted-task

Conversation

@littlejawa

Copy link
Copy Markdown

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

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

Copy link
Copy Markdown
Author

@rhartman93 @simonbaird - you've been working with us on dm-verity in the past. Can you help here?
If we need to sync with #294, I'm fine with it, just want to make sure we can get this on time for our release (end of Nov).

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