public inbox for [email protected]  

help / color / mirror / Atom feed

From: Mikael Kjellström <[email protected]>
To: Andrew Dunstan <[email protected]>
To: Tom Lane <[email protected]>
To: [email protected]
Subject: Re: Reminder: spin up REL_11_STABLE on your buildfarm animals
Date: Mon, 9 Jul 2018 11:35:45 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>


On 2018-07-08 17:52, Andrew Dunstan wrote:

> If you're running the modern way via run_branches.pl with 
> branches_to_build set to ALL or HEAD_PLUS_LATESTn then this should just 
> happen without owner intervention when a new branch is created. So I 
> assume that all these are either running not using run_branches.pl. or 
> have hardcoded lists of branches in their config files.

Yes, I am using the run_build.pl on cron-schedule as I run most of the 
my animals on the same virtualized host and I need to control when 
different animal/branches builds so they don't overlap.  If I would run 
run_branches.pl I have no control over how long each run will take and 
it's hard to schedule.

But I've updated all my animals to include V11 now so they should all 
report in on the next run.

> Probably not best practice.

Probably not.  But see above.

/Mikael

view thread (6+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Reminder: spin up REL_11_STABLE on your buildfarm animals
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox