Re: buildfarm and "rolling release" distros

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: buildfarm and "rolling release" distros
Date: 2014-07-01 18:02:02
Message-ID: CA+TgmoZKp_WNRdjy0STgqV14vMMYYpMrM9wV-csLQOQKg+UfKA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 1, 2014 at 12:49 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> I've always been a bit reluctant to accept buildfarm members that are
> constantly being updated, because it seemed to me that it created something
> with too many variables. However, we occasionally get requests from people
> who want to run on such platforms, and I'm also a bit reluctant to turn away
> willing volunteers. We have one such application now in hand.
>
> What do people think about this. Is it valuable to have? Do we have enough
> stability from the buildfarm members that are not auto-updated that we can
> accept a certain number of auto-updating members, where, if something
> breaks, and it doesn't break elsewhere, then we suspect that something that
> got upgraded broke the build?
>
> I'm also not sure how to designate these machines. The buildfarm server
> metadata isn't designed for auto-updating build platforms. But no doubt if
> necessary we can come up with something.

Off-hand, it seems like we could give it a try, and abandon the effort
if it proves too problematic.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vik Fearing 2014-07-01 18:45:25 Re: Cluster name in ps output
Previous Message Peter Geoghegan 2014-07-01 18:00:44 Re: Fresh initdb contains a few deleted B-Tree pages