Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade
Date
Msg-id 40712083-b1a5-4aa6-b35f-d648f7207319@eisentraut.org
Whole thread Raw
In response to Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
Responses Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade
List pgsql-hackers
On 05.06.25 10:04, Nazir Bilal Yavuz wrote:
> Thomas Munro off-list mentioned that the Windows CI image is actually
> running on Server 2022, even though the task name still refers to
> Server 2019. He also suggested upgrading the compiler from Visual
> Studio 2019 to Visual Studio 2022.

Some of the tasks for the other operating systems name the version, some 
don't.  We have recently removed the version from the FreeBSD task. 
Should we remove the versions from the task name everywhere, to avoid 
having further mismatches?

> A PR [1] to upgrade the compiler to VS 2022 is ready in Andres'
> pg-vm-images repository (where the CI images are built). This VS 2022
> image passes all tests for both MinGW [2] and Meson & Ninja [2]. Once
> it's merged, the CI images will automatically start using the VS 2022
> compiler.

Hmm, for the purposes of [0], I think it might be better to keep the 
image at VS 2019 for now.  Unless there are specific reasons why VS 2022 
would be of use now?

[0]: 
https://www.postgresql.org/message-id/flat/01a69441-af54-4822-891b-ca28e05b215a%40eisentraut.org




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [19] Proposal: function markers to indicate collation/ctype sensitivity
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade