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

  • From: kallisti5 <kallisti5@xxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 21 Feb 2017 08:05:30 -0600

On 2017-02-21 03:37, Adrien Destugues wrote:

21 février 2017 08:49 "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> a écrit:
Am 21/02/2017 um 07:14 schrieb Adrien Destugues:

On Mon, Feb 20, 2017 at 09:22:20PM -0600, kallisti5 wrote:
Feel free to try it out and provide feedback. Each buildmaster instance is
chroot isolated within a container and all the stateful information is
stored on the local machine's filesystem, so the containers should address
*most* of our current issues.

The only issue I was aware of with the buildmaster is it needs a
machine to host it. I'm curious how Docker solves that? :D It's "the
Cloud", right?

They can be run wherever we want. Cloud, baron, your desktop. All the buildmaster
setup is pre-configured. Pass an architecture and you have a command prompt
ready to manage builders + fire off builds. "It's just a chroot"

You can still use the buildmaster stuff without the container as well.

Not sure how often I said this already, but please use vmweb for this.
But no one gave me a way to login there.

I sent out an email on the progress of the vmweb decom + cleanup to
haiku-sysadmin and haiku-web.

It's been mentioned that vmweb is on it's last legs multiple times by multiple
people.

This entire process has been extended over months because the Inc. was
unable to get enough votes to purchase a new $20/mo VM anywhere "and get it done".
Instead we've been forced to squeeze all this crap onto a 10-year old abused VM
running an unsupported version of openSUSE.

 -- Alex

Other related posts:

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