ci: fix dunfell github actions

[bachp]

This fixes github actions for the dunfell branch

[agherzan]

@bachp friendly ping on this one

[bachp]

@agherzan Unfortunatly github actions doesn't work well with yocto builds. I haven't found a reliable way that doesn't run into timeouts all the time. Ideas are welcome

[agherzan]

@bachp I have finally migrated to GitHub actions with a BSP layer. I will test drive the setup for a while but it looks like everything is in place for now. You can take a look. I'm planning to define some yocto-specific actions so we can reuse bits across the ecosystem.

agherzan/meta-raspberrypi#1005

[bachp]

@agherzan I have CI working via kas, but it still takes a lot of time. Ideally there would be a way to cache some of the sstate between runs.

[agherzan]

@bachp not easy if you use default workers. I'm not sure what setup you have here.

[moto-timo]

@bachp I noticed you got a successful build with CDN SSTATE_MIRROR for mickeldore. I was contemplating if the 10GB limit on cache@vx would also be enough to help us keep under the dreaded timeout.

[bachp]

@moto-timo Unfortunately I'm not happy with the any of the current CI setups I tried.

I haven't tried cache@vx but so far I found that the sstate doesn't fit well with the method of uploading and downloading the cache. As the cache keeps growing.

But you got me thinking about an idea. Maybe a workflow that would work is the following:

1. Download and extract the cache locally to ${SOMEDIR}/sstate (usually done automatically by caching service).
2. Rename from ${SOMEDIR}/sstate to ${SOMEDIR}/sstate-prev
3. Configure yocto to use ${SOMEDIR}/sstate-prev as SSTATE_MIRROR
4. Uplaod ${SOMEDIR}/sstate so it is ready for the next run

I haven't tried this yet.

[bachp]

Obsolete now