Re: Reminder: spin up REL_11_STABLE on your buildfarm animals - Mailing list buildfarm-members

From Mikael Kjellström
Subject Re: Reminder: spin up REL_11_STABLE on your buildfarm animals
Date
Msg-id a2c29dd7-2c16-3bbb-c567-ac5bf94cfeae@mksoft.nu
Whole thread Raw
In response to Re: Reminder: spin up REL_11_STABLE on your buildfarm animals  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: Reminder: spin up REL_11_STABLE on your buildfarm animals  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List buildfarm-members
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


buildfarm-members by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Reminder: spin up REL_11_STABLE on your buildfarm animals
Next
From: Andrew Dunstan
Date:
Subject: Re: Reminder: spin up REL_11_STABLE on your buildfarm animals