public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dave Page <[email protected]>
To: Tom Lane <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: [email protected]
Subject: Re: Enable CI on postgres/postgres github repo?
Date: Fri, 7 Jan 2022 14:55:28 +0000
Message-ID: <CA+OCxoytLBq0jjTv=hgGK6Rk9HBx+XVKCN7=592ZPrHc0U05Og@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CA+OCxoyvHr-7zD1vKAB45hk7eN16xNhBjx1Y63xcMh+4VRm09A@mail.gmail.com>
<[email protected]>
On Wed, Jan 5, 2022 at 3:17 PM Tom Lane <[email protected]> wrote:
> Dave Page <[email protected]> writes:
> > On Tue, Jan 4, 2022 at 11:51 PM Andres Freund <[email protected]>
> 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".
>
OK, well from what I can tell, all the reports are delivered on the Cirrus
or Github sites, so it'll take zero effort to ignore it :-)
I've enabled it for the postgres/postgres repo, so those that are
interested can take a look:
https://cirrus-ci.com/github/postgres/postgres/
There's nothing to see there at the moment; I guess we need a commit to
trigger a build.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Enable CI on postgres/postgres github repo?
In-Reply-To: <CA+OCxoytLBq0jjTv=hgGK6Rk9HBx+XVKCN7=592ZPrHc0U05Og@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox