-
Notifications
You must be signed in to change notification settings - Fork 0
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
Automatically test built Docker containers for open-BMC #25
Comments
Automatically testing those containers on GitHubs runners might not be possible due to them requiring a lot of disk space. I guess we will have to blindly create those and then test those locally. Generally speaking the container to do so is not that complex. Building OpenBMC is a matter of having a sane base e.g. Ubuntu as we use on the other containers, the dependencies as usual (mostly python, gcc toolchain, etc.) and then run two commands: |
Might be interesting idea to look into KAS which does not build everything from source, but from pre-compiled distro repositories.
|
I recently had a discussion about extending CI storage in ephemeral runners using online network storage which might solve the issue of being limited to 14G storage BUT will in turn slow down file operations even further. The idea would be to mount something like an S3 bucket into the runner and then set the working directory into the mounted network storage, effectively enlarging the disk space to what is needed. But I still don't think this is the best solution here. |
While that is an option, I fear it would slow down the build my at least an entire order of magnitude. |
Sorry, closed by mistake. |
We could add OpenBMC containers but not test them automatically. Technically all that is needed for those is python and the average build tools like gcc and such. From a point of complexity it is somewhat comparable to building Linux. |
Simple container with single stage? That would be fine by me. |
No description provided.
The text was updated successfully, but these errors were encountered: