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 ) id 1fcUOS-0008Vv-6J for buildfarm-members@arkaria.postgresql.org; Mon, 09 Jul 2018 11:31:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fcUOO-0007ml-L1 for buildfarm-members@arkaria.postgresql.org; Mon, 09 Jul 2018 11:31:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fcUOO-0007me-CU for buildfarm-members@lists.postgresql.org; Mon, 09 Jul 2018 11:31:44 +0000 Received: from mail-qk0-x243.google.com ([2607:f8b0:400d:c09::243]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fcUOJ-0008QB-HO for buildfarm-members@postgresql.org; Mon, 09 Jul 2018 11:31:43 +0000 Received: by mail-qk0-x243.google.com with SMTP id v17-v6so7032998qkb.11 for ; Mon, 09 Jul 2018 04:31:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=fMFa7eaOCYJUZhsylQWkZHgbZQIIto319ny9cupYEuU=; b=E3/yaIDLAUPFqDWrBCUhUeMHajUS8eAmq7h06ONzSy/3TGAmGMUDN+dNc3Q4GFHM+K y/KRFwlGXHCMwR90W/As8WTEShHJR6WmEYdcHKDnnRVb2+LLsMRPWrSF7+1rM8h++tsh Cw/gkz01IcxTZ9AyqC5YKmHPTzT8i7H8U0a0YHoZIPX8LWgAgfKFtEv+Dt3lhUr9MRSe 4eU1EtOQPVGLMga8H6/WuBc59iqFaqK8uU3ihnlBwqlpxoQv8G7iVW8qSzjzW0Yxf0HV ok5rWZt3red+Z6/95tDrIUVRSxJKQ3fV39VKnVAF/kWBit2QqpE/Ti363HnDlDfLG7XH VaFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=fMFa7eaOCYJUZhsylQWkZHgbZQIIto319ny9cupYEuU=; b=bmtlyX2+KEarjhq5299DdHRkRxWIwL80tyqvvLwxx9EKrwgArnRoVdktJut5pm5DN6 1sqU/stWGdYH2krbagfxokKnKz/3V3y9dgBpn5FUytklBzHDzOxpU8MvA7nAkSdTA8Ma sz1qXDohfXJqOFknZFAVGjZDqu+eDKhxpqoQWItPiGc7ovz5UuuxjkE6/Vt8UZPhr+0G WvIvOMFmJafu3lN1pCclVJ0p6QZI7UwUJoudIInUiiG7EwVYnRT5McITHAbP6OHEiHIr JpHKcouyIzKv5j3qV3SeRvMB3C/FS16KvmQAqMmprF8jg2TDBD6fMy07a9f49u9JXrsc hkHg== X-Gm-Message-State: APt69E2aLb6lEEK+rpYCtd5eGsCnEs/HUzCD/LHu0/yYh9vHjpkutrgK m0v8yJ3i7SaFHa16Au8/NdYHXn+nw+ba7PNWNcA9YJjla0gLHDMDKrK0JrF0PTPrwGvm+G+6xC7 5bYq6U8h2I7HhRASGX7R0ATGSAuzTV38Y0fOD2P+FJ3aukOIwr6M7QOPomiihFFIl3exEnmF+k6 6p7UCmHyKsEqrDWMr0gg== X-Google-Smtp-Source: AAOMgpdz7F6+kMB1CvBnFFPqy6gIxr0tsZczqNWvsSiL9LWr7fglOGIidm1MMd9aAth7V2KZvVWZQw== X-Received: by 2002:a37:70a:: with SMTP id 10-v6mr17835384qkh.393.1531135897458; Mon, 09 Jul 2018 04:31:37 -0700 (PDT) Received: from [192.168.10.146] ([98.122.175.38]) by smtp.gmail.com with ESMTPSA id p4-v6sm6740257qkc.52.2018.07.09.04.31.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Jul 2018 04:31:36 -0700 (PDT) From: Andrew Dunstan X-Google-Original-From: Andrew Dunstan Subject: Re: Reminder: spin up REL_11_STABLE on your buildfarm animals To: =?UTF-8?Q?Mikael_Kjellstr=c3=b6m?= , Tom Lane , buildfarm-members@postgresql.org References: <71293.1530992999@sss.pgh.pa.us> <5efff0db-b252-c974-a8f0-e7e0c3172f2c@2ndQuadrant.com> Message-ID: <400d7809-1084-d9bf-61f1-bd66d29d3393@2ndQuadrant.com> Date: Mon, 9 Jul 2018 07:31:36 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-MW List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 07/09/2018 05:35 AM, Mikael Kjellström wrote: > > 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. > run_branches has a global lock that protects against concurrent runs of different animals. You just point all the animals on the machine at the same lock directory. I have several machines with this setup. See global_lock_dir in the sample config file. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services