Re: Continuous integration on Windows?

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Continuous integration on Windows?
Date: 2017-10-13 12:09:55
Message-ID: CAEepm=0_YWP1SZ1c0F_hPT2hrmmZ7zjBptv9DG3qXTvFkn+7TQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 13, 2017 at 1:42 PM, Andrew Dunstan
<andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
> Well, as you can see here the appveyor.yml file can live outside the
> tree that's being built.

Here's a Wiki page where I hope we can collect how-to information on
this general topic:

https://wiki.postgresql.org/wiki/Continuous_Integration

I tried your appveyor.yml, and added:

test_script:
- cd src\tools\msvc && vcregress check

That much I could figure out just by reading our manual and I could
see that it worked first time, but to make this really useful I guess
we'd have to teach it to dump out resulting regression.diffs files and
backtraces from core files (as the Travis CI version accessible from
that page does).

--
Thomas Munro
http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2017-10-13 12:42:05 Re: Still another race condition in recovery TAP tests
Previous Message Robert Haas 2017-10-13 11:54:26 Re: [COMMITTERS] pgsql: Fix traversal of half-frozen update chains