On 11/14/22 15:54, Sebastian Kuzminsky wrote:
The difficulty with building and testing LinuxCNC in docker containers
or in off-the-shelf VMs (as in Github Actions) is that our 'RTAI'
configuration needs a special kernel, and needs to load and unload
kernel modules to run & test LinuxCNC.
(Unlike RTAI, the 'uspace' config *can* be built and tested in docker
containers, though we don't currently do that in our Github Actions.
The LinuxCNC/mesaflash project builds in docker in Github Actions, and
I agree, it's great and super convenient.)
In order to support testing LinuxCNC on RTAI the buildbot uses custom
VMs which i created a long time ago and maintain poorly. It all runs
on hardware in my house, on my local network, so I am reluctant to
open it up to a more collaborative mode of development/maintenance.
Seb,
Yes you only have so much time and thankfully you have donated so much
of it over the years and also your home based sever buildbot.
Alec already mentioned supporting and maintaining the RTAI packages.
I'll check back with him on what he recommends we do for a public
build-bot. He spent the last coupe of years automating cloud setups and
even has been included in a patent on doing so.
Rod has already found us some free VM space. Alec didn't see a problem
with getting it all connected and setup. He also works closely with Andy
and building RTAI.
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
