Received: from malur.postgresql.org ([2a02:16a8:dc51::56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <buildfarm-members-owner+archive@lists.postgresql.org>)
	id 1fcSaZ-0001Yp-1h
	for buildfarm-members@arkaria.postgresql.org; Mon, 09 Jul 2018 09:36:11 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <buildfarm-members-owner+archive@lists.postgresql.org>)
	id 1fcSaX-0003dR-Kh
	for buildfarm-members@arkaria.postgresql.org; Mon, 09 Jul 2018 09:36:09 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <mikael.kjellstrom@mksoft.nu>)
	id 1fcSaX-0003dK-Bp
	for buildfarm-members@lists.postgresql.org; Mon, 09 Jul 2018 09:36:09 +0000
Received: from yoda.llamalab.com ([194.14.207.58] helo=yoda.mksoft.nu)
	by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <mikael.kjellstrom@mksoft.nu>)
	id 1fcSaT-0001A4-OG
	for buildfarm-members@postgresql.org; Mon, 09 Jul 2018 09:36:08 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mksoft.nu;
 s=20151129;
	h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject;
 bh=ruta9AEedWZbOQh9vMyVQB/pp8Az+laiWuPjhlxM3z4=;
	b=A2rij7inwftxBNHupWo9CeDJxqGBXHPOFWQb6i3VB8W0LbBm+yXjx2goqQVoflHRYEgOxovOmhwnFhH1FWktLpUNxEoqjbSm1g2oVI6gTgDWb4EwM7tqTk58MJRqyBWh9UQeFgn/liQp1Gd5HbQgxiJxBRwhGH7s2CUe1nEUQg4HLcYJd/lkYLE+Q/vjwQRMIaUVtdSCCrxvhvwxiZutmo8CcxRiwmeTAnRm3Z+4BJNZByduMETSIAZodJW1zV0pRDfkWWDOaHEFigTDQqJJbMNzgah62Ei0WTkLXXQrZ2cc35XXNvMJNIbTqDmmWu3DEZntg9tjp1m+LxoH4A52bQ==;
Received: from c83-251-79-56.bredband.comhem.se ([83.251.79.56]
 helo=[10.100.0.2])
	by yoda.mksoft.nu with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128)
	(Exim 4.80)
	(envelope-from <mikael.kjellstrom@mksoft.nu>)
	id 1fcSaE-0004Km-1I; Mon, 09 Jul 2018 11:36:01 +0200
Subject: Re: Reminder: spin up REL_11_STABLE on your buildfarm animals
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>,
 Tom Lane <tgl@sss.pgh.pa.us>, buildfarm-members@postgresql.org
References: <71293.1530992999@sss.pgh.pa.us>
 <5efff0db-b252-c974-a8f0-e7e0c3172f2c@2ndQuadrant.com>
From: =?UTF-8?Q?Mikael_Kjellstr=c3=b6m?= <mikael.kjellstrom@mksoft.nu>
Message-ID: <a2c29dd7-2c16-3bbb-c567-ac5bf94cfeae@mksoft.nu>
Date: Mon, 9 Jul 2018 11:35:45 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.0
MIME-Version: 1.0
In-Reply-To: <5efff0db-b252-c974-a8f0-e7e0c3172f2c@2ndQuadrant.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
List-Id: <buildfarm-members.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:buildfarm-members@lists.postgresql.org>
List-Owner: <mailto:buildfarm-members-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/buildfarm-members>
Precedence: bulk


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