Automatically test built Docker containers for open-BMC
AtomicFS opened this issue · 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: . setup $BOARD_NAME followed by bitbake obmc-phosphor-image. After that grab a coffee in the neighboring city by bike and go back, if you're lucky the process has finished by then.
Might be interesting idea to look into KAS which does not build everything from source, but from pre-compiled distro repositories.
- docs
- Blogpost: Setting Up Yocto Projects with kas