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

From: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade
Date: 2025-10-31 06:58:03
Message-ID: CAN55FZ3j-LUTm8EiVqocaxTPDsDzgOR7UOjdUk85aWGR8XT5_w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Thu, 30 Oct 2025 at 20:26, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> On 2025-09-15 11:50:07 +0300, Nazir Bilal Yavuz wrote:
> > v3 is attached. I forgot to update the MinGW task's name in the
> > previous versions, it is done now.
>
> I pushed the s/2019/2022/ portion now.

Thanks!

> I'm still not convinced by the OS enablement for vs*...

What do you think about introducing CI_TASK_ONLY like in the [1]?

[1] https://postgr.es/m/CAN55FZ2d4Qa%3DZXpuDxnoUn28G%2BZ0e06LwWS1qpZ-UNRAsWY2VQ%40mail.gmail.com

--
Regards,
Nazir Bilal Yavuz
Microsoft

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Lukas Fittl 2025-10-31 07:18:04 Re: Stack-based tracking of per-node WAL/buffer usage
Previous Message Shinya Kato 2025-10-31 06:31:40 Report oldest xmin source when autovacuum cannot remove tuples