Re: [Pgbuildfarm-members] Release 4.17 of the PostgreSQL Buildfarm client

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PGBuildFarm <pgbuildfarm-members(at)pgfoundry(dot)org>
Subject: Re: [Pgbuildfarm-members] Release 4.17 of the PostgreSQL Buildfarm client
Date: 2016-02-21 00:40:57
Message-ID: 4778.1456015257@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Changes of note: ...
> * fix trigger_exclude pattern in build-farm.conf

> ... If you don't need any of the other changes (most people probably won't)

FWIW, I think the fix in the default trigger_exclude pattern is important
and most buildfarm owners will want to adopt it. The intention of that
pattern has always been to not run a build cycle if only doc or .po files
changed, but it was done wrong, resulting in running a build anyway for
doc-only changes. So unless you are running "build_docs" or "dist" tests,
you'll want that fix to save useless builds.

(OTOH, if you are running such tests, you'll want to annotate the fact
that you're intentionally using a nondefault pattern, so you don't break
it later.)

regards, tom lane

In response to

Responses

Browse buildfarm-members by date

  From Date Subject
Next Message Andrew Dunstan 2016-02-21 14:37:39 Re: [Pgbuildfarm-members] Release 4.17 of the PostgreSQL Buildfarm client
Previous Message Andrew Dunstan 2016-02-20 23:59:58 Release 4.17 of the PostgreSQL Buildfarm client

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2016-02-21 02:05:06 Deferrable check constraints
Previous Message Tatsuo Ishii 2016-02-21 00:13:23 Re: Tutorial document