-
Notifications
You must be signed in to change notification settings - Fork 22
ci(feat): add mkosi os image building #780
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
base: main
Are you sure you want to change the base?
Conversation
4b7ca15 to
922098e
Compare
| @@ -0,0 +1,305 @@ | |||
| From 4597a8c36a5cd043fa27acfe90297a80c9a59f59 Mon Sep 17 00:00:00 2001 | |||
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.
Is this Patch required because mkosi doesnt have support for Amazon linux?
If yes what is the maintenance overhead for the patch, in the sense do we need to change if mkosi gets updated or changes some pattern?
This is a bit concerning if this is the case.
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.
The patch is taken from a PR which got abandoned. I don't anticipate much maintenance burden in mkosi since Amazon Linux is essentially treated as Fedora by mkosi, with a few small changes.
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.
Can we add documentation about the reference for the patch in readme.
And probably also the caveats for fixes done for AL2023.
Lets say a new AL version comes out do we have to redo the changes, but probably not relevant as don't see Al2023 going out of life any time soon
| @@ -0,0 +1,120 @@ | |||
| name: Build OS | |||
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.
Seems to have many parts, although it doesnt serves our use case but would using fedora have solved the different patches and configs we have to set?
My concern is maintainability of this infra.
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.
Can you be more specific?
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.
If we had taken fedora would it have made the configs simpler?
deps/mkosi/README.md
Outdated
|
|
||
| ### Custom Package Building | ||
|
|
||
| - **`al2023-build/`**: Directory containing infrastructure for building custom AL2023 packages |
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.
nit: folder rename to al2023-custom-package-build
deps/mkosi/build.sh
Outdated
| @@ -0,0 +1,204 @@ | |||
| #!/bin/bash | |||
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.
this script probably can be split into single responsibility parts.
Signed-off-by: Justin Alvarez <[email protected]>
Signed-off-by: Justin Alvarez <[email protected]>
922098e to
ef89ea2
Compare
|
@Shubhranshu153 addressed comments in latest revision. Had to rebase to fix the commit name |
Description of changes
Adds scripts, configuration, and a GitHub workflow for building Finch OS images using mkosi.
Testing done
Created working images for macOS and Windows using the GitHub Workflow: https://github.com/pendo324/finch-core/actions/runs/19875268071?pr=1
TODO
These are items which need to be done, but have been split off from this PR because it has already gotten too large:
Integrate these images with our existing tooling in finch/finch-core (e.g. make sure these images are tested)
Set up a schedule / triggers for automatically rebuilding the OS image
Integrate the dependencies in these images with existing version control / tracking mechanisms
I've reviewed the guidance in CONTRIBUTING.md
License Acceptance
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.