Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade

From: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade
Date: 2025-06-05 08:04:49
Message-ID: CAN55FZ1OsaM+852BMQDJ+Kgfg+07knJ6dM3PjbGbtYaK4qwfqA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

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.

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.

Two patches are attached, the first one is for fixing server names and
the second one is for upgrading the VS compiler version in the task
name. Please note: the PR and second patch should be committed
simultaneously to avoid mismatches (e.g., a VS 2019 task running with
a VS 2022 compiler, or vice versa).

Any feedback would be appreciated.

[1] https://github.com/anarazel/pg-vm-images/pull/114
[2] https://cirrus-ci.com/build/5095727501672448

--
Regards,
Nazir Bilal Yavuz
Microsoft

Attachment Content-Type Size
0001-ci-Update-Windows-task-names-to-reflect-Server-2022.patch text/x-patch 1.1 KB
0002-ci-Update-Windows-task-name-to-reflect-VS-2022.patch text/x-patch 935 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-06-05 08:12:18 Re: [19] Proposal: function markers to indicate collation/ctype sensitivity
Previous Message Magnus Hagander 2025-06-05 08:04:06 Re: Potential issue in listExtensions()