[Pgbuildfarm-members] triggering builds - new skin

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgbuildfarm-members(at)pgfoundry(dot)org
Subject: [Pgbuildfarm-members] triggering builds - new skin
Date: 2004-12-30 15:30:18
Message-ID: 41D41F0A.5010901@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members


I am thinking of making the trigger for doing a new build a little less
sensitive by excluding docs and translation files from consideration.
Changes in them would still be added when a new build is done.

Currently the test for not doing a build says:

if ($last_status && ! @changed_files)

The would become something like:

my @trigger_files = grep { ! m'/(doc|po)/' } @changed_files;
if ($last_status && ! @trigger_files)

The advantage would be that we would only trigger builds when more
significant things (i.e. code!) change, so the build history would
become more useful, with less dross.

Thoughts?

Lastly, many many thanks to Michael Glaesemann for the lovely new skin
for the buildfarm web site. Also, some of you might not be aware that
the web site is provided by CommandPrompt - many thanks also go to them.

cheers

andrew

Responses

Browse buildfarm-members by date

  From Date Subject
Next Message Kris Jurka 2004-12-31 04:58:26 Re: [Pgbuildfarm-members] triggering builds - new skin
Previous Message Andrew Dunstan 2004-12-21 13:06:43 [Pgbuildfarm-members] release 1.04 of buildfarm client is available