Re: [PATCH] Add GitLab CI to PostgreSQL
От | Gurjeet Singh |
---|---|
Тема | Re: [PATCH] Add GitLab CI to PostgreSQL |
Дата | |
Msg-id | CABwTF4UcKJ-uNO-NEFnWhAKYg2pc6=MpPY6U8AWcFxRzmY1v6w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Add GitLab CI to PostgreSQL (Daniel Gustafsson <daniel@yesql.se>) |
Список | pgsql-hackers |
On Thu, Jul 6, 2023 at 11:27 AM Daniel Gustafsson <daniel@yesql.se> wrote: > > > On 6 Jul 2023, at 20:10, Gurjeet Singh <gurjeet@singh.im> wrote: > > > I can > > imagine if cfbot was developed against some other CI, it's very likely > > that we'd be using that other CI instead of Cirrus. > > The CFBot originally used Travis, but switched in late 2020 when Travis almost > over night become hard to use for open source projects: > > https://github.com/macdice/cfbot/commit/a62aa6d77dd4cc7f0a5549db378cd6f1cf25c0e2 Thanks for providing the historical context! A for-profit entity, despite their best intentions, and sometimes by no fault of their own, may not survive. It's not that a non-profits are guaranteed to survive, but the conditions they operate in are drastically different than those of for-profit ones. > These systems come and go, and each have their quirks. I'm sure the community has seen enough of such disappearances over the years, which is why I was surprised to see the adoption of Cirrus in core (after I had stopped paying attention to Postgres hackers list for a few years). Having read that whole discussion, though, I do see the immense value Cirrus CI provides. > Having options is good, > but maintaining multiple ones isn't necessarily a free fire-and-forget type of > thing for the community. By not adopting at least one other CI, it'd seem like the community is favoring Cirrus over others; and that doesn't feel good. Best regards, Gurjeet http://Gurje.et
В списке pgsql-hackers по дате отправления: