Closed Ruadhri17 closed 5 months ago
To add Github Action builds, I think I'd be necessary to research the following:
On Yocto Project summit from May 2022, There was a presentation on using Github Actions in Yocto layers. Here is link to the video and theirs solution. I think we can create something similar. I noticed that if the dependencies are cached, next builds will be much faster. However, it will require some space and I don't know if we are allowed to use so much.
I have prepared exemplary workflow for building Yocto that is available in my forked repository. It seems to work properly, however due to a disc space limit for basic GitHub plan I cannot finish the build. I think we don't want to use paid options so the only solution is self-hosted runner. I have seen some combinations in other layers that use docker containers on self-hosted runners to build several distros on different architectures. Then we could also load thin-edge tests and run them after successful builds.
Builds will be covered by the meta-tedge-project repository: https://github.com/thin-edge/meta-tedge-project/actions.
A dedicated github runner will be used due to the builds taking such as long time (and requiring a large cache)
The meta-tedge-project github actions are in place and build projects which use this layer now.
Add github action build that test if layer compiles and works as intended.