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
if I understand correctly, you build all ROS packages on GitHub runners and aarch64-linux packages are built via qemu. This must take very long time. At our university, I've got a few powerful servers, whose power I could donate to building ROS packages. Specifically, I have an 80-core aarch64-linux machine and a 32-core x86_64-linux machine. Would you be interested in using these to speed-up development in this repo?
I see several possibilities how to use them. The simplest one, which can be working very quickly, is that the servers can be used as nix remote builders. Either for CI running on GitHub, or even for you personal Hydra (I think you have one somewhere). Another option would be to run Hydra (or other CI system) on those servers to and integrate it in this repo.
Let me know what do you think and we can then discuss details such as security, trustworthiness etc.
The text was updated successfully, but these errors were encountered:
Hi @lopsided98 ,
if I understand correctly, you build all ROS packages on GitHub runners and aarch64-linux packages are built via qemu. This must take very long time. At our university, I've got a few powerful servers, whose power I could donate to building ROS packages. Specifically, I have an 80-core aarch64-linux machine and a 32-core x86_64-linux machine. Would you be interested in using these to speed-up development in this repo?
I see several possibilities how to use them. The simplest one, which can be working very quickly, is that the servers can be used as nix remote builders. Either for CI running on GitHub, or even for you personal Hydra (I think you have one somewhere). Another option would be to run Hydra (or other CI system) on those servers to and integrate it in this repo.
Let me know what do you think and we can then discuss details such as security, trustworthiness etc.
The text was updated successfully, but these errors were encountered: