public inbox for [email protected]help / color / mirror / Atom feed
Enable CI on postgres/postgres github repo? 5+ messages / 3 participants [nested] [flat]
* Enable CI on postgres/postgres github repo? @ 2022-01-04 23:51 Andres Freund <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: Andres Freund @ 2022-01-04 23:51 UTC (permalink / raw) To: [email protected] Hi, 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. Arguably it doesn't add that much, because cfbot runs builds using the .cirrus.yml file all the time, but to me it still seems worthwhile: For one, it actually does run windows builds sooner after a commit than the buildfarm often does... Greetings, Andres Freund [1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=93d97349461347d952e8cebdf62f5aa84b4bd... [2] https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob_plain;f=src/tools/ci/README ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Enable CI on postgres/postgres github repo? @ 2022-01-05 09:15 Dave Page <[email protected]> parent: Andres Freund <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: Dave Page @ 2022-01-05 09:15 UTC (permalink / raw) To: Andres Freund <[email protected]>; +Cc: [email protected] On Tue, Jan 4, 2022 at 11:51 PM Andres Freund <[email protected]> wrote: > Hi, > > 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. > > Arguably it doesn't add that much, because cfbot runs builds using the > .cirrus.yml file all the time, but to me it still seems worthwhile: For > one, > it actually does run windows builds sooner after a commit than the > buildfarm > often does... > > Greetings, > > Andres Freund > > [1] > https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=93d97349461347d952e8cebdf62f5aa84b4bd... > [2] > https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob_plain;f=src/tools/ci/README Seems reasonable to me - no cost, and very little effort. I'm happy to set it up if noone objects. -- Dave Page Blog: https://pgsnake.blogspot.com Twitter: @pgsnake EDB: https://www.enterprisedb.com ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Enable CI on postgres/postgres github repo? @ 2022-01-05 15:17 Tom Lane <[email protected]> parent: Dave Page <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: Tom Lane @ 2022-01-05 15:17 UTC (permalink / raw) To: Dave Page <[email protected]>; +Cc: Andres Freund <[email protected]>; [email protected] 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". regards, tom lane ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Enable CI on postgres/postgres github repo? @ 2022-01-07 14:55 Dave Page <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: Dave Page @ 2022-01-07 14:55 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Andres Freund <[email protected]>; [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 ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Enable CI on postgres/postgres github repo? @ 2022-01-07 22:13 Andres Freund <[email protected]> parent: Dave Page <[email protected]> 0 siblings, 0 replies; 5+ messages in thread From: Andres Freund @ 2022-01-07 22:13 UTC (permalink / raw) To: Dave Page <[email protected]>; +Cc: Tom Lane <[email protected]>; [email protected] Hi, On 2022-01-07 14:55:28 +0000, Dave Page wrote: > On Wed, Jan 5, 2022 at 3:17 PM Tom Lane <[email protected]> wrote: > > Dave Page <[email protected]> writes: > > 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. Due to cfbot we kind of have to anyway... > > 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.) It should be a bit better now. All *.log, *.diffs, regress_log* files are preserved for 90 days for failing testruns. You can navigate to them at the top of the page of a result. It's still annoying to see the precise test that failed in a parallel check-world invocation. But that's a much more general issue than just in CI checks :(. > > 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 wondered if it could make sense to forward those reports to the buildfarm status page, via a dedicated animal. But it doesn't seem that important. > I've enabled it for the postgres/postgres repo Thanks! > 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. Yep. Happened since: https://cirrus-ci.com/github/postgres/postgres, two successful runs. Greetings, Andres Freund ^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2022-01-07 22:13 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2022-01-04 23:51 Enable CI on postgres/postgres github repo? Andres Freund <[email protected]> 2022-01-05 09:15 ` Dave Page <[email protected]> 2022-01-05 15:17 ` Tom Lane <[email protected]> 2022-01-07 14:55 ` Dave Page <[email protected]> 2022-01-07 22:13 ` Andres Freund <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox