From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: Nico Williams <nico@cryptonector.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Robbie Harwood <rharwood@redhat.com>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>
Subject: Re: [PATCH v16] GSSAPI encryption support
Date: Mon, 11 Jun 2018 13:31:12 -0400
Message-ID: <10fecbaa-24d0-cd86-952d-92827929a85c@2ndQuadrant.com> (raw)
In-Reply-To: <20180611171315.GA23356@localhost>
References: <jlg1tgq1ktm.fsf@thriss.redhat.com>
<jlg1se287n3.fsf@redhat.com>
<CAEepm=2NkNjV97hThgHOQjk9j719wjFxVozs9LVn3YqW9egFgw@mail.gmail.com>
<jlg603c6chf.fsf@redhat.com>
<jlgr2lz4l6l.fsf@redhat.com>
<CAEepm=2+FbEJsVX5B6fYW7UBXpF6osaixSXn2A297WgP+rEhxA@mail.gmail.com>
<20180607210058.GE24501@localhost>
<CAEepm=0E8ga2McBB8fuC92+R0Hj=4TxR3kWR2fpJkwGSbcZF4g@mail.gmail.com>
<CA+TgmoYmPutv1kiU7cbNp7MGCW0ECofVXoGNi6yYPMHB_8z=Mw@mail.gmail.com>
<20180611171315.GA23356@localhost>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andrew.dunstan@2ndquadrant.com, nico@cryptonector.com, robertmhaas@gmail.com, thomas.munro@enterprisedb.com, rharwood@redhat.com, michael.paquier@gmail.com, sfrost@snowman.net
Subject: Re: [PATCH v16] GSSAPI encryption support
In-Reply-To: <10fecbaa-24d0-cd86-952d-92827929a85c@2ndQuadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox