Greetings Erich, Erich Steinböck wrote: > I thought there was some ooRexx VM server that David used to run. Did > that end up going away? > > When David left as ooRexx dev, he took the box with him to his new Redhat > engagement
Thanks for that context of what happened. > So I best just do my own thing in VirtualBox on my own system? > > Even if you machine isn't online 24x7, it may still be worth to set it up as > a Jenkins slave. I think we already have a few slaves with limited > availability. OK to attach VM's running in VirtualBox as Jenkins slaves? I will only be firing up the VM's one at a time in order to produce builds, then shutting back down. Since you are working already on 16.04, I will focus on 14.04 and 12.04, both x64 and i386. I am building fresh VM's which I can set up the C++ compiler environment in. (I do not normally set up such... I am an ooRexx programmer, not C++! ;-) ) And I am specifically setting up images of the base ISO of the particular version, not the .1, .2, etc... updated releases. The updated releases sometimes come with newer kernels, which I would not want the ooRexx package to suddenly be dependent on having been built with. Oh, and first I will catch up packages for the current stable v4.2.0. Can you crank out 16.04 packages of v4.2.0, or are you not interested in such and I should spin up 16.04 VM's to capture such? I am thankful, -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
