Re: Adding CI to our tree

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: 0010203112132233 <boekewurm(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: Adding CI to our tree
Date: 2021-10-02 02:41:13
Message-ID: CA+hUKGLqxOFOrZ7ffcCQwrkJqZwFqXRcgL=FGVbpwuKX29h7bA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Oct 2, 2021 at 1:10 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2021-10-02 01:49:39 +0200, 0010203112132233 wrote:
> > Furthermore, after looking it through, I think that Cirrus is an
> > unfortunate choice as a CI platform of preference, as you cannot use
> > it without access to Github (which is problematic for people located
> > in certain localities due to USA regulations).
>
> I agree that it's not optimal that cirrus isn't available on all git hosting
> platforms. Hence saying that I think it's likely we'd end up adding a few more
> platforms over time. If we factor the meat of the work into an helper script,
> so that the CI specific bit is just a couple invocation of that script, it's
> not a lot of overhead to have 2-3 CI platforms.

BTW I think they might be considering supporting other code hosting
platforms (at least they ask for feedback on this at
https://cirrus-ci.org/guide/quick-start/ ).

> > Lastly, I consider CI configuration similar to IDE configuration: each
> > developer has their own preferred tools which they use, but we don't
> > favour one over the other. We don't include IDE-specific configuration
> > files either, or at least, the policy is against that.

We have some files in the tree to help users of Emacs, vim, and even
make github format text the way we like.

Personally, I think that if someone is willing to develop and maintain
high quality CI control files that work for any public
free-for-open-source CI system, then we should accept them too. It
costs very little to have a few .something.yml files at top level. If
at any point the file for a given provider is showing signs of being
unmaintained, we can remove it. Personally, I'm willing and able to
help maintain Cirrus control files, not least because it means that
cfbot will become simpler and will match exactly what you can get in
your own github account.

I really like Cirrus because our project has more portability concerns
than most, and most other CIs are like "we got both kinds, country and
western!". I wanted to add FreeBSD to cfbot, which is something they
advertise as a feature, but it looks like at least 3 other OSes we
target would probably work just as well given a suitable image.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Fone 2021-10-02 03:48:24 Re: pgcrypto support for bcrypt $2b$ hashes
Previous Message Tatsuo Ishii 2021-10-02 02:33:47 Problem with CF app?