[haiku-development] Re: Haiku buildmasters, now easy

  • From: Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 21 Feb 2017 21:52:00 +0100

Am 21/02/2017 um 17:55 schrieb kallisti5:

it's a vm.  I'm down for reinstalling it as a buildmaster... that was
always one
of the options.   Just concerning when we're asked to use vmweb as-is.
We're not sure it will upgrade properly at this point :-)

Since it currently runs anyway, and has resources left, I see no downside in just using it as a build master as is, either.
When we don't need it anymore as vmweb, just replace it with a new one, that then (at first, at least) only hosts the build master.

Nope, the entire process has been "extended over months" because the
Inc. sees no reason to buy more resources when we already have enough
that aren't used properly.
It's just the sensible and responsible thing to do.
Eh.  I'm pretty sure nobody outside of the Inc. would be upset over a
$10/mo vm until this stuff is cleaned up properly. I could have a set of
buildmasters going in ~15 minutes.

Again, the VM is there to be used, and that didn't change within the last months. Of course, it wouldn't be very expensive to get a new even only temporary VM for this; but I think it's way more work to set up a new temporary VM for this when we already have one or two that could be used (vm-site would also have been a candidate).

Hasn't it updated like the rest of the VMs? If not, why not? That's
*not* the responsibility of the Inc., btw. it just offers the
resources.
It hasn't been upgraded because there hasn't been a full-time admin since
Olta left. (Just lots of part time admins (myself included))

I was under the impression that all VMs had been updated from time to time. Or is that OpenSUSE version just no longer supported, and no one "took the leap" yet?

Bye,
   Axel.

Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 02-2017