MIME-Version: 1.0
References: <20220104235112.bnx6pczz7h3jbu2o@alap3.anarazel.de>
 <CA+OCxoyvHr-7zD1vKAB45hk7eN16xNhBjx1Y63xcMh+4VRm09A@mail.gmail.com>
 <43299.1641395861@sss.pgh.pa.us>
In-Reply-To: <43299.1641395861@sss.pgh.pa.us>
From: Dave Page <dpage@pgadmin.org>
Date: Fri, 7 Jan 2022 14:55:28 +0000
Message-ID: 
 <CA+OCxoytLBq0jjTv=hgGK6Rk9HBx+XVKCN7=592ZPrHc0U05Og@mail.gmail.com>
Subject: Re: Enable CI on postgres/postgres github repo?
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>, pgsql-www@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000005129cb05d4ff2e3a"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BOCxoytLBq0jjTv%3DhgGK6Rk9HBx%2BXVKCN7%3D592ZPrHc0U05Og%40mail.gmail.com>
Precedence: bulk

--0000000000005129cb05d4ff2e3a
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 5, 2022 at 3:17 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:

> 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".
>

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

--0000000000005129cb05d4ff2e3a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 5, 2022 at 3:17 PM Tom La=
ne &lt;<a href=3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>&gt; wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204=
,204,204);padding-left:1ex">Dave Page &lt;<a href=3D"mailto:dpage@pgadmin.o=
rg" target=3D"_blank">dpage@pgadmin.org</a>&gt; writes:<br>
&gt; On Tue, Jan 4, 2022 at 11:51 PM Andres Freund &lt;<a href=3D"mailto:an=
dres@anarazel.de" target=3D"_blank">andres@anarazel.de</a>&gt; wrote:<br>
&gt;&gt; Now that the CI patch has been merged [1], perhaps it&#39;d make s=
ense to<br>
&gt;&gt; enable<br>
&gt;&gt; that on the postgres/postgres mirror on github? See [2] for instru=
ctions.<br>
<br>
&gt; Seems reasonable to me - no cost, and very little effort. I&#39;m happ=
y to set<br>
&gt; it up if noone objects.<br>
<br>
I&#39;m kind of down on this actually.=C2=A0 Either it will be a waste of c=
ycles<br>
because no one looks at the reports, or PG hackers will have to learn<br>
to read and interpret a second source of build failure reports.=C2=A0 We ha=
ve<br>
a lot of accumulated knowledge about the buildfarm, plus ways to examine<br=
>
past failures, none of which would exist here as far as I&#39;ve gathered<b=
r>
from experience with the cfbot.=C2=A0 (And the cfbot&#39;s reports definite=
ly suck<br>
in usability compared to the farm --- failures often omit critical logs,<br=
>
and what there is is crammed into a single badly-formatted web page.)<br>
<br>
I guess the bottom line for me is &quot;set it up if you want, but don&#39;=
t<br>
expect me to pay any attention to it&quot;.<br></blockquote><div><br></div>=
<div>OK, well from what I can tell, all the reports are delivered on the Ci=
rrus or Github sites, so it&#39;ll take zero effort to ignore it :-)</div><=
div><br></div><div>I&#39;ve enabled it for the postgres/postgres repo, so t=
hose that are interested can take a look:</div><div><br></div><div><a href=
=3D"https://cirrus-ci.com/github/postgres/postgres/">https://cirrus-ci.com/=
github/postgres/postgres/</a></div><div><br></div><div>There&#39;s nothing =
to see there at the moment; I guess we need a commit to trigger a build.</d=
iv><div>=C2=A0</div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"=
><div dir=3D"ltr">Dave Page<br>Blog: <a href=3D"https://pgsnake.blogspot.co=
m" target=3D"_blank">https://pgsnake.blogspot.com</a><br>Twitter: @pgsnake<=
br><br>EDB: <a href=3D"https://www.enterprisedb.com" target=3D"_blank">http=
s://www.enterprisedb.com</a><br><br></div></div></div>

--0000000000005129cb05d4ff2e3a--