10 comments

• 

  Jonathan Gillette May 9, 2024 6:50 am 0

  collapse this comment copy link to this comment

  super minor but the “new agent” screen has the wrong version of the agent in the setup directions for the x64 zip:
  PS C:\agent> Add-Type -AssemblyName System.IO.Compression.FileSystem ; [System.IO.Compression.ZipFile]::ExtractToDirectory(“$HOME\Downloads\vsts-agent-win-x64-3.225.0.zip”, “$PWD”)

  x86/mac/linux are correct
  PS C:\agent> Add-Type -AssemblyName System.IO.Compression.FileSystem ; [System.IO.Compression.ZipFile]::ExtractToDirectory(“$HOME\Downloads\vsts-agent-win-x86-3.225.3.zip”, “$PWD”)

  • 

    Gloridel Morales May 9, 2024 10:58 am 0

    collapse this comment copy link to this comment

    Hi Jonathan, thank you for installing the Azure DevOps Server 2022.2 release candidate and reporting this. We will address this with the final version of Azure DevOps Server 2022.2.

• 

  Maple May 10, 2024 7:28 am 0

  collapse this comment copy link to this comment

  Does Update 2 include a fix for this issue with Update 1? https://developercommunity.visualstudio.com/t/Known-issue:-Agent-version-does-not-upda/10534065

  • 

    Gloridel Morales May 10, 2024 10:22 am 0

    collapse this comment copy link to this comment

    Hi, this issue has been fixed with Update 2.

• 

  Tore Østergaard Jensen (TORE) May 13, 2024 1:04 am 0

  collapse this comment copy link to this comment

  Looking forward to fixes and new features 🙂

  When you get to update the features timeline with the features introduced with 2022.2, then you might want to review the items market with ‘Future’ too:
  https://learn.microsoft.com/en-us/azure/devops/release-notes/features-timeline-released
  An example is the “Trigger CI builds from YAML”, which I figure have been included in ADO Server for many years:
  https://learn.microsoft.com/en-us/azure/devops/release-notes/2018/apr-16-vsts#trigger-ci-builds-from-yaml

  Another example is “Removing older images in Azure Pipelines hosted pools” which I guess should be marked with “N/A” instead of “Future”:
  https://learn.microsoft.com/en-us/azure/devops/release-notes/2020/sprint-164-update#removing-older-images-in-azure-pipelines-hosted-pools

  • 

    Gloridel Morales May 15, 2024 3:45 pm 0

    collapse this comment copy link to this comment

    Thank you Tore for the feedback.

• 

  Tore Østergaard Jensen (TORE) May 14, 2024 3:07 am 0

  collapse this comment copy link to this comment

  Hi

  I wonder if you somehow know the status of the test framework included with this release. We have seen multiple problems in each release and although some things are fixed, then it just seems like new problems are added.

  Current issue – Wrong failure naming for DynamicData:
  https://developercommunity.visualstudio.com/t/AZDO-portal-can-report-incorrectly-faile/10497992

  Current issue – Rerun failure:
  https://github.com/microsoft/azure-pipelines-tasks/issues/16187

  Previous issue – DataTestMethod rerun not correct
  https://developercommunity.visualstudio.com/t/VSTest-rerun-logic-have-issues-with-Data/10292590

  • 

    Bohdan Janousek May 16, 2024 4:14 am 0

    collapse this comment copy link to this comment

    Thanks for the feedback. Both reported issues are related the VSTest@2 task. As soon as the root cause for each of the two cases will be identified and fixed, we’ll release new version of that task that will resolve these problems.

• 

  Tore Østergaard Jensen (TORE) May 17, 2024 1:19 am 0

  collapse this comment copy link to this comment

  Will the team be on-site next week during Build in Seattle?

  Would love to chat if you have time 🙂

  • 

    Gloridel Morales May 17, 2024 8:33 am 0

    collapse this comment copy link to this comment

    Some of us will be there. See you at Build 🙂