-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: install mkosi from repository #2233
ci: install mkosi from repository #2233
Conversation
Install mkosi from the upstream project to align s390x and amd64 builds. Signed-off-by: Magnus Kulke <magnuskulke@microsoft.com>
dd0eb3f
to
3187e27
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally on Fedora 40. Thanks @mkulke !
@stevenhorsman the e2e tests will fail since the workflow and the Makefile were edited |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of code tidying suggestions, but otherwise looks good assuming the tests pass
Good point - can we test (some of it) on a fork repo? |
3187e27
to
77652b3
Compare
yup, see PR description |
Sorry! |
more recent version of mkosi can use Profile & Architecture in matches clauses. Signed-off-by: Magnus Kulke <magnuskulke@microsoft.com>
77652b3
to
291e3f3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks!
As discussed in the last community call, we can adopt the installation method of the s390x builds and use it also for the amd64 builds. this allows us to use the profile feature available in more recent versions of mkosi and simplify some things.
here would be a successful build on a fork. due to the pull-request-target logic there will be a mismatch between Makefile (on PR branch) and github-actions workflow (on main), so it doesn't make sense to run e2e tests here.