caching and upload artifacts to external storage #1
Description
Nice work @HtmMhmd
I believe you have created this layer for a specific purpose, which is great. Starting with a minimal layer containing all the required layers, depending on the specific hardware, is a good approach. I have used it for such a purpose, and it helped me as a good starting point for a base project that I am planning to increment.
So after forking your repo, I found some issues that I believe would help you too:
- Caching the layers' repos, downloads, and sstate_cache would help save runner minutes. I did improve them till I reached almost 20 mins instead of your current approach of building everything from scratch each time, which took around 6 hours to build
- I would also recommend saving artifacts at an external storage to keep the increments you are working on, with a version number for proper versioning and source code tracking, which would be helpful for future enhancements
I could help with that if you would like my contribution.