I double the sentiment for virtualization if your intent is a continuous integration system for testing and artifact building. As Justin mentioned, the frequency of the runs adjusts the value of VM vs physical. I don’t know if Travis CI supports every OS on your list, but it might and you could set up a testing framework with it. If it’s open source work it could also be free through them and you wouldn’t have to worry about computer costs at all.
> On May 24, 2019, at 9:39 AM, Justin Sherrill <[email protected]> > wrote: > > Get a single large machine and virtualize each one of the > environments. It won't be as fast, but that may not matter if you are > only building, say, weekly. > > On Thu, May 23, 2019 at 11:45 PM Pierre Abbat > <[email protected]> wrote: >> >> I'm planning to get several small computers so that I can test my software on >> several OSes. One will compile binaries for Windows; the others will run >> OpenBSD, NetBSD, probably FreeBSD, and maybe DragonFly (I already have a >> DragonFly box, but it's slow compared to my laptop). I'm looking at these: >> https://www.newegg.com/Barebone-Mini-Computers/Category/ID-3 >> How can I make sure that all the hardware works on all the BSDs? >> >> The reason I say "probably FreeBSD" is that another computer I'm going to get >> is a Power9 box from Raptor for big-endian testing. I know of two OSes that >> are big-endian on Power9: Adélie Linux and FreeBSD. However, while it is Tier >> 1 on Adélie, it is Tier 2 on FreeBSD. So I may or may not set it up as dual- >> boot. >> >> Pierre >> -- >> I believe in Yellow when I'm in Sweden and in Black when I'm in Wales. >> >> >>
