Windows Server 2019 in UNH CI Testing?

Windows Server 2019 in UNH CI Testing?

[Patrick Robb]

Hello Tyler,

Windows Server 2019 mainstream end  of support date is January 2024,
and extended end of support date is January 2029.

Currently at UNH we have two VMs (windows server 2019 and 2022) both
running the Clang-LLVM & MinGW-64 compile jobs.

The server 2022 machine also runs the custom MSVC compile jobs that we
set up in Fall 2023.

So, with Windows Server 2019 reaching end of regular support, should
we discontinue CI on this system, or maintain it until (potentially)
2029 when it reaches end of extended support?

I am okay with either, I just don't necessarily understand how
significant the regular vs extended support distinction is, and
whether the results from the older system are still valuable for
developers.

Cheers.

-Patrick

https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2019

Re: Windows Server 2019 in UNH CI Testing?

[Stephen Hemminger]

On Thu, 25 Jul 2024 15:14:37 -0400
Patrick Robb <probb@iol.unh.edu> wrote:

> Hello Tyler,
> 
> Windows Server 2019 mainstream end  of support date is January 2024,
> and extended end of support date is January 2029.
> 
> Currently at UNH we have two VMs (windows server 2019 and 2022) both
> running the Clang-LLVM & MinGW-64 compile jobs.
> 
> The server 2022 machine also runs the custom MSVC compile jobs that we
> set up in Fall 2023.
> 
> So, with Windows Server 2019 reaching end of regular support, should
> we discontinue CI on this system, or maintain it until (potentially)
> 2029 when it reaches end of extended support?
> 
> I am okay with either, I just don't necessarily understand how
> significant the regular vs extended support distinction is, and
> whether the results from the older system are still valuable for
> developers.
> 
> Cheers.
> 
> -Patrick
> 
> https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2019


Since Windows is a monoculture, having older version is not very interesting.
What is important is make sure both tool chains (MSVC and Clang) work.

Re: Windows Server 2019 in UNH CI Testing?

[Tyler Retzlaff]

hi Patrick,

On Thu, Jul 25, 2024 at 03:14:37PM -0400, Patrick Robb wrote:
> Hello Tyler,
> 
> Windows Server 2019 mainstream end  of support date is January 2024,
> and extended end of support date is January 2029.
> 
> Currently at UNH we have two VMs (windows server 2019 and 2022) both
> running the Clang-LLVM & MinGW-64 compile jobs.
> 
> The server 2022 machine also runs the custom MSVC compile jobs that we
> set up in Fall 2023.
> 
> So, with Windows Server 2019 reaching end of regular support, should
> we discontinue CI on this system, or maintain it until (potentially)
> 2029 when it reaches end of extended support?

i don't see a lot of utility in maintaining the server 2019 any further.
i think it is fine to consolidate and use the server 2022 vm.

we will want to maintain the build with all 3 toolchains (which i think
is what we already have on the 2022 setup?) and continue running the unit
tests for the llvm/clang build (and mingw if we already do?)

ty

> 
> I am okay with either, I just don't necessarily understand how
> significant the regular vs extended support distinction is, and
> whether the results from the older system are still valuable for
> developers.
> 
> Cheers.
> 
> -Patrick
> 
> https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2019

Re: Windows Server 2019 in UNH CI Testing?

[Patrick Robb]

On Tue, Aug 6, 2024 at 1:43 AM Tyler Retzlaff
<roretzla@linux.microsoft.com> wrote:
> i don't see a lot of utility in maintaining the server 2019 any further.
> i think it is fine to consolidate and use the server 2022 vm.
>
> we will want to maintain the build with all 3 toolchains (which i think
> is what we already have on the 2022 setup?) and continue running the unit
> tests for the llvm/clang build (and mingw if we already do?)
>

Okay, thanks Stephen and Tyler. We will discontinue usage of the
server 2019 VM, and run the 3 toolchains from serve 2022.

Re: Windows Server 2019 in UNH CI Testing?

[Tyler Retzlaff]

On Tue, Aug 06, 2024 at 12:38:32PM -0400, Patrick Robb wrote:
> On Tue, Aug 6, 2024 at 1:43???AM Tyler Retzlaff
> <roretzla@linux.microsoft.com> wrote:
> > i don't see a lot of utility in maintaining the server 2019 any further.
> > i think it is fine to consolidate and use the server 2022 vm.
> >
> > we will want to maintain the build with all 3 toolchains (which i think
> > is what we already have on the 2022 setup?) and continue running the unit
> > tests for the llvm/clang build (and mingw if we already do?)
> >
> 
> Okay, thanks Stephen and Tyler. We will discontinue usage of the
> server 2019 VM, and run the 3 toolchains from serve 2022.

somewhat related when you have time in your schedule i think you can
also upgrade the compiler on the server 2022 vm to visual studio
17.10.x. the non-preview / release version of the compiler now contains
everything needed for msvc + dpdk.

ty

Re: Windows Server 2019 in UNH CI Testing?

[Patrick Robb]

On Tue, Aug 6, 2024 at 12:47 PM Tyler Retzlaff
<roretzla@linux.microsoft.com> wrote:
>
> On Tue, Aug 06, 2024 at 12:38:32PM -0400, Patrick Robb wrote:
> > On Tue, Aug 6, 2024 at 1:43???AM Tyler Retzlaff
> > <roretzla@linux.microsoft.com> wrote:
> > > i don't see a lot of utility in maintaining the server 2019 any further.
> > > i think it is fine to consolidate and use the server 2022 vm.
> > >
> > > we will want to maintain the build with all 3 toolchains (which i think
> > > is what we already have on the 2022 setup?) and continue running the unit
> > > tests for the llvm/clang build (and mingw if we already do?)
> > >
> >
> > Okay, thanks Stephen and Tyler. We will discontinue usage of the
> > server 2019 VM, and run the 3 toolchains from serve 2022.
>
> somewhat related when you have time in your schedule i think you can
> also upgrade the compiler on the server 2022 vm to visual studio
> 17.10.x. the non-preview / release version of the compiler now contains
> everything needed for msvc + dpdk.
>
> ty

Perfect. For context, we are no longer on the Preview version (we did
an upgrade some months ago), but without checking I'm guessing there
is an even newer version available now. We will look.