On 2023-07-04 Tu 19:44, Newhouse, Robin wrote:
@font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:11.0pt; font-family:"Calibri",sans-serif; mso-ligatures:standardcontextual;}span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri",sans-serif; color:windowtext;}.MsoChpDefault {mso-style-type:export-only;}div.WordSection1 {page:WordSection1;}Hello!
I propose the attached patch to be applied on the 'master' branch
of PostgreSQL to add GitLab CI automation alongside Cirrus CI in the PostgreSQL repository.
It is not intended to be a replacement for Cirrus CI, but simply suggestion for the
PostgreSQL project to host centrally a Gitlab CI definition for those who prefer to use
it while developing/testing PostgreSQL.
The intent is to facilitate collaboration among GitLab users, promote standardization
and consistency, and ultimately, improve testing and code quality.
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?
If we're going to do this then arguably we should also be supporting GitHub Actions and who knows what other CI frameworks. There is a case for us special casing Cirrus CI because it's used for the cfbot.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com