You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently finally built my own CI for my project and one thing that I had to solve for was not to create a fresh Sming build environment for every single build run.
I decided to create a container with Sming the necessary toolchains fully installed, submodules intiialized and at least the core modules built for every SMING_SOC. This way, when I do a matrix build, I only have to pull that container to have everything in place.
It would be great to have that container built right from the Sminghub/Sming repo, ideally for the relevant branches (releases, develop, master), have them uploaded to a container registry so that other CIs could just pull them as an up-to-date build environment.
If you're happy to do that, I'd be happy to help out with it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I recently finally built my own CI for my project and one thing that I had to solve for was not to create a fresh Sming build environment for every single build run.
I decided to create a container with Sming the necessary toolchains fully installed, submodules intiialized and at least the core modules built for every SMING_SOC. This way, when I do a matrix build, I only have to pull that container to have everything in place.
It would be great to have that container built right from the Sminghub/Sming repo, ideally for the relevant branches (releases, develop, master), have them uploaded to a container registry so that other CIs could just pull them as an up-to-date build environment.
If you're happy to do that, I'd be happy to help out with it.
Beta Was this translation helpful? Give feedback.
All reactions