From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
---|---|
To: | Nico Williams <nico(at)cryptonector(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Robbie Harwood <rharwood(at)redhat(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
Subject: | Re: [PATCH v16] GSSAPI encryption support |
Date: | 2018-06-11 17:31:12 |
Message-ID: | 10fecbaa-24d0-cd86-952d-92827929a85c@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 06/11/2018 01:13 PM, Nico Williams wrote:
>
> Well, all the free CIs like Travis and Appveyor do it this way. You
> don't have to *use* it just because the .yml files are in the source
> tree. But you have to have the .yml files in the source tree in order
> to use these CIs. It'd be nice to be able to point somewhere else for
> them, but whatever, that's not something we get much choice in at this
> time.
>
That's not true, at least for Appveyor (can't speak about travis - I
have no first hand experience). For appveyor, you can supply a custom
appveyor.yml file, which can be a complete URL. In fact, if you use a
plain git source as opposed to one of the managed git services it
supports, you have to do it that way - it ignores an appveyor.yml in
your repo. I found this out the very hard way over the last few days,
and they very kindly don't warn you at all about this.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2018-06-11 17:33:39 | Re: Spilling hashed SetOps and aggregates to disk |
Previous Message | Andres Freund | 2018-06-11 17:14:09 | Re: Spilling hashed SetOps and aggregates to disk |