From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dave Page <dpage@pgadmin.org>
cc: Andres Freund <andres@anarazel.de>, pgsql-www@lists.postgresql.org
Subject: Re: Enable CI on postgres/postgres github repo?
In-reply-to: 
 <CA+OCxoyvHr-7zD1vKAB45hk7eN16xNhBjx1Y63xcMh+4VRm09A@mail.gmail.com>
References: <20220104235112.bnx6pczz7h3jbu2o@alap3.anarazel.de>
 <CA+OCxoyvHr-7zD1vKAB45hk7eN16xNhBjx1Y63xcMh+4VRm09A@mail.gmail.com>
Comments: In-reply-to Dave Page <dpage@pgadmin.org>
	message dated "Wed, 05 Jan 2022 09:15:45 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <43298.1641395861.1@sss.pgh.pa.us>
Date: Wed, 05 Jan 2022 10:17:41 -0500
Message-ID: <43299.1641395861@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/43299.1641395861%40sss.pgh.pa.us>
Precedence: bulk

Dave Page <dpage@pgadmin.org> writes:
> On Tue, Jan 4, 2022 at 11:51 PM Andres Freund <andres@anarazel.de> wrote:
>> Now that the CI patch has been merged [1], perhaps it'd make sense to
>> enable
>> that on the postgres/postgres mirror on github? See [2] for instructions.

> Seems reasonable to me - no cost, and very little effort. I'm happy to set
> it up if noone objects.

I'm kind of down on this actually.  Either it will be a waste of cycles
because no one looks at the reports, or PG hackers will have to learn
to read and interpret a second source of build failure reports.  We have
a lot of accumulated knowledge about the buildfarm, plus ways to examine
past failures, none of which would exist here as far as I've gathered
from experience with the cfbot.  (And the cfbot's reports definitely suck
in usability compared to the farm --- failures often omit critical logs,
and what there is is crammed into a single badly-formatted web page.)

I guess the bottom line for me is "set it up if you want, but don't
expect me to pay any attention to it".

			regards, tom lane