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

Hi,

On 2025-09-15 11:50:07 +0300, Nazir Bilal Yavuz wrote:
> On Thu, 11 Sept 2025 at 17:55, Jacob Champion
> <jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> >
> > On Thu, Sep 11, 2025 at 7:18 AM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> > > I don't think we need this level of complication. We already have the
> > > situation that for example "linux" covers several tasks
> >
> > Recently, I've wished that it were otherwise; if I'm debugging a
> > Meson-only test failure in Linux, I don't want to burn credits running
> > Autoconf.
>
> I agree with Jacob. I think it would be better if each task had its
> own tag. I left it as "vs2019" for now.

I don't really agree that this is something that needs to be changed as part
of this. Or that the CI_OS_ONLY is really the way to tackle this.

Perhaps we should just have CI_TASK_ONLY and CI_OS_ONLY?

Greetings,

Andres Freund