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
Reduce the time to deploy an Andino bot in a fully functional system.
Alternatives considered
Probably there are many out there, like from a bash script, having an image of the SD card, etc. etc. etc.
However, I think that starting by having a dockerized version that can be built in a host machine (x86) that mimics the build procedure in the final architecture (arm64) allows to catch issues with incompatible processes and test many things in CI (not yet, Github Actions doesn't support arm64 yet).
Implementation suggestion
I would consider building in stages and providing multiple images:
Image for development in RPI, but with no workspace specific dependency. (A)
Image that clones the repo, installs the workspace, builds and tests the packages in andino. (B)
Image that mounts the repo as a volume and it is suitable for continuous development. (C)
Desired behavior
Reduce the time to deploy an Andino bot in a fully functional system.
Alternatives considered
Probably there are many out there, like from a bash script, having an image of the SD card, etc. etc. etc.
However, I think that starting by having a dockerized version that can be built in a host machine (x86) that mimics the build procedure in the final architecture (arm64) allows to catch issues with incompatible processes and test many things in CI (not yet, Github Actions doesn't support arm64 yet).
Implementation suggestion
I would consider building in stages and providing multiple images:
B depends on A.
C depends on A.
A and B can be distributed via Github, probably.
Additional context
Running https://github.com/Ekumen-OS/andino/tree/humble/andino_hardware is tedious. At least, we can reduce the burden by providing the specifics of software packages installed in a docker container.
The text was updated successfully, but these errors were encountered: