Message-ID: <80542823-5318-12e9-d306-5bbe35a689b1@linaro.org>
Date: Fri, 25 Aug 2023 11:34:18 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.14.0
Subject: Re: [PATCH] Add native windows on arm64 support
Content-Language: en-GB
To: Michael Paquier <michael@paquier.xyz>
Cc: Andrew Dunstan <andrew@dunslane.net>, Mike Holmes
 <mike.holmes@linaro.org>, Tom Lane <tgl@sss.pgh.pa.us>,
 Andres Freund <andres@anarazel.de>, Ian Lawrence Barwick
 <barwick@gmail.com>, Thomas Munro <thomas.munro@gmail.com>,
 Julien Rouhaud <rjuju123@gmail.com>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
 robhenry@microsoft.com, "Jonathan S. Katz" <jkatz@postgresql.org>,
 Alvaro Herrera <alvherre@2ndquadrant.com>,
 Amit Kapila <amit.kapila16@gmail.com>, Lina Iyer <lina.iyer@linaro.org>
References: <3864856.1683347740@sss.pgh.pa.us>
 <20230508191731.mtt3mpgrr6v2br7t@awork3.anarazel.de>
 <461478.1683575921@sss.pgh.pa.us>
 <00b0804c-3e5d-22b5-c7dd-3efe6d43d78d@dunslane.net>
 <ZFwqBTSHVkGGyAyJ@paquier.xyz>
 <b3d2540e-3fdd-6184-35bd-83e84b0da5a9@linaro.org>
 <c03799fe-78ab-d1b9-35a8-9f1e28563d18@linaro.org>
 <6d533c8f-9158-33e2-d476-f15bc4e055f1@linaro.org>
 <ZN6e9KGtu+X63HQe@paquier.xyz>
 <219d1120-f383-6e63-1954-b3c0ebefa61c@linaro.org>
 <ZOh/t+7RJibPBHqh@paquier.xyz>
From: Anthony Roberts <anthony.roberts@linaro.org>
In-Reply-To: <ZOh/t+7RJibPBHqh@paquier.xyz>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/80542823-5318-12e9-d306-5bbe35a689b1%40linaro.org>
Precedence: bulk

Thanks for the link - that looks basically the same as what we do for 
CMake (option 2), so should be relatively easy.

I will have a chat to relevant people about setting a machine up 
properly for it.

Thanks,
Anthony

On 25/08/2023 11:17, Michael Paquier wrote:
> On Fri, Aug 25, 2023 at 10:40:39AM +0100, Anthony Roberts wrote:
>> Which of these are you looking for us to provide:
>>
>> * A machine for you to directly access (via a VPN)
>> * A machine we just run a worker script on that automatically picks up the
>> builds as required
>> * Us to do downstream CI
>>
>> All are possible, but preferably not option 1, as it would mean straight up
>> pulling out a machine from our build farm, and it has to go through all
>> sorts of approvals internally. If it's the only way forward I can kick it up
>> the chain though.
>>
>> Option 2 and 3 are ones we do for various other projects (ie. 2 - CMake, 3 -
>> OpenSSL)
> The community has its own CI facility.  Here is a link of how to set
> up a machine:
> https://wiki.postgresql.org/wiki/PostgreSQL_Buildfarm_Howto
>
> And all the results are published by the maintainers of the machines
> on a periodic basis where the buildfarm client code is set:
> https://buildfarm.postgresql.org/cgi-bin/show_status.pl
>
> The final result would be for you to maintain the machine so as we are
> able to see if anything breaks with it.  Adding extra dependencies to
> the build like OpenSSL would be nice, but based on the contents of the
> patch to add this port that does not seem mandatory to me, either.
>
> Once the machine is ready, you will need to request a buildfarm
> machine name and a key to be able to begin publishing the reports of
> the builds to the community buildfarm.  Once the machine is ready to
> go, just let me know and I'd be OK to merge the patch (I still want to
> do a final review of it in case I've missed something, but I can move
> on with that before the buildfarm machine is set up).
> --
> Michael