Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update/Add Windows Server 2022 image #3138

Closed
1 of 8 tasks
ykuijs opened this issue Apr 9, 2021 · 6 comments
Closed
1 of 8 tasks

Update/Add Windows Server 2022 image #3138

ykuijs opened this issue Apr 9, 2021 · 6 comments

Comments

@ykuijs
Copy link

ykuijs commented Apr 9, 2021

Tool information

Area for Triage:
Windows Server 2019 has a very specific performance issue when running PowerShell unit tests, that cause my unit tests to require twice the amount of time. The issue also exists in Windows 10 and I have been able to validate that improvements were implemented in the 2004 build of Windows 10 and Windows Server (bi-annual versions, not 2019).

I know Windows Server 2022 is still in Prreview, but I am hoping a VM image can be created because this issue is seriously impacting efficiency in our project.

Question, Bug, or Feature?:
Question

Virtual environments affected

  • Ubuntu 16.04
  • Ubuntu 18.04
  • Ubuntu 20.04
  • macOS 10.15
  • macOS 11.0
  • Windows Server 2016 R2
  • Windows Server 2019
  • Windows Server 2022

Can this tool be installed during the build?
No

Tool installation time in runtime
N/A

Are you willing to submit a PR?
N/A

@maxim-lobanov
Copy link
Contributor

Hello @ykuijs , thank you for your proposal!
We definitely will add Windows Server 2022 when the stable version is released.

As for the adding new image while it is in preview, we would like to keep this issue opened for a while to track popularity of this request.
Usually, adding new images is not fast and simple process.

@EwoutH
Copy link
Contributor

EwoutH commented May 3, 2021

This might be interesting: Announcing a New Windows Server Container Image Preview

@AtOMiCNebula
Copy link
Contributor

When this is done, can we take the opportunity to pick new baselines for some of the legacy-default packages installed into the windows-2016/-2019 images? The whole mess with the Azure PowerShell modules is what comes to mind for me (we install v2.1.0 and v6.13.1, but only v2.1.0 is in PSModulePath), but maybe there are others. I believe the reason we don't want to change the installed defaults is for fear of breaking changes, but releasing a new OS image/family is the best time to make those breaking changes, and if we don't land the change early, we lose the ability to land it easily for another few years.

@miketimofeev
Copy link
Contributor

@AtOMiCNebula yes, there is a chance. We've made similar changes during Ubuntu 20 onboarding.

@maxim-lobanov
Copy link
Contributor

Hello everyone!

Windows Server 2022 image is available for Azure DevOps and GitHub users! 🚀
Please find more details in #3949

GitHub Actions

jobs:
  jobName:
    runs-on: windows-2022

Azure DevOps

jobs:
- job: jobName
  pool:
    vmImage: windows-2022

@ykuijs
Copy link
Author

ykuijs commented Aug 24, 2021

Thanks @maxim-lobanov, I am indeed able to use Windows Server 2022 and my pipelines now complete over 50% quicker!!

m-tmatma added a commit to m-tmatma/SendARP that referenced this issue Dec 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants