Re: [PATCH] Add GitLab CI to PostgreSQL

Поиск
Список
Период
Сортировка
Искать
От
Peter Eisentraut
Тема
Re: [PATCH] Add GitLab CI to PostgreSQL
Дата
Msg-id
fb4d96ac-5b6e-891f-b84e-b3dcdf6d98e4@eisentraut.org
Ответ на
Список
Дерево обсуждения
[PATCH] Add GitLab CI to PostgreSQL "Newhouse, Robin" <robinnew@amazon.com>
Re: [PATCH] Add GitLab CI to PostgreSQL Andres Freund <andres@anarazel.de>
Re: [PATCH] Add GitLab CI to PostgreSQL Andrew Dunstan <andrew@dunslane.net>
Re: [PATCH] Add GitLab CI to PostgreSQL Gurjeet Singh <gurjeet@singh.im>
Re: [PATCH] Add GitLab CI to PostgreSQL Daniel Gustafsson <daniel@yesql.se>
Re: [PATCH] Add GitLab CI to PostgreSQL Gurjeet Singh <gurjeet@singh.im>
Re: [PATCH] Add GitLab CI to PostgreSQL Matthias van de Meent <boekewurm+postgres@gmail.com>
Re: [PATCH] Add GitLab CI to PostgreSQL Andrew Dunstan <andrew@dunslane.net>
Re: [PATCH] Add GitLab CI to PostgreSQL Peter Eisentraut <peter@eisentraut.org>
On 06.07.23 13:32, Andrew Dunstan wrote:
>>> This seems very RedHat-centric, which I'm not sure is a good idea. Also, shouldn't at least some of these recipes call dnf and dnf-builddep instead of yum and yum-build-dep?
>> I don't think it's bad to add an automated test suite for redhat-based images?
> 
> I didn't suggest it wasn't just that the coverage should be broader.

If we were to accept this (or other providers besides Cirrus), then I 
think they should run the exact same configurations that we have for 
Cirrus right now (or possibly subsets or supersets, depending on 
availability and capabilities).  Those have been put there with a lot of 
care to get efficient and reasonably broad coverage.  There is no point 
in starting that whole journey over again.

If someone thinks we should have more coverage for Red Hat-based 
platforms, then let's put that into the Cirrus configuration.  That 
should be independent of the choice of CI provider.



В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата:
От: Andres Freund
Дата:
FAQ