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
signature.asc
Description: PGP signature
