Re: [PATCH v16] GSSAPI encryption support

Andrew Dunstan <andrew.dunstan@2ndquadrant.com>

From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: Nico Williams <nico@cryptonector.com>, Robert Haas <robertmhaas@gmail.com>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>, Robbie Harwood <rharwood@redhat.com>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>, Michael Paquier <michael.paquier@gmail.com>, Stephen Frost <sfrost@snowman.net>
Date: 2018-06-11T17:31:12Z
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



Commits

  1. GSSAPI encryption support

  2. Fix typo