-
Notifications
You must be signed in to change notification settings - Fork 866
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
Using the latest azure-pipelines-agent v2.193.1 on premises - Does not recognize Visual Studio 2022 RC #3567
Comments
Hello @rizi, could you please attach full debug logs of your execution of visual studio build task? |
@tatyana-kostromskaya I think at least two ps1 scripts(maybe more) need to be changed to support VS 2022 (17.x): Could you please tell me how to get a full log. Do I have to set a special variable for a full log or something else? Br |
To get debug log, you need to run your pipeline with variable system.debug = true.
Yes, we need to additionally change these scripts to have correct list of capabilities, but VisualStudio capabilities should not affect "VisualStudio build task" because it contains its own logic to get latest installed versions of VS and msbuild. |
@tatyana-kostromskaya I would also expect to see Visual Studio 2022 in the drop down box (Visual Studio Versions), see the attached picture. I think the tasks on the azure devops server (on premises) need to be updated as well, have a look at this issue (microsoft/azure-pipelines-tasks#15051 (comment)), but it seems this has only be done for azure devops services and not for the on premises version, what do you think (as I already mentioned, all tasks are affected (build, restore, test, ..)? Thx for your time an patience! |
For on-premise solutions (Azure DevOps Server) tasks updates are deployed with Azure DevOps Server updates, that should be updated manually. I can only suggest you to update all tasks you are interested in manually. I can provide you ready build of tasks and instructions how to update these tasks in your organization. |
@tatyana-kostromskaya Do I need a new version of azure-pipelines-agent as well, or just the tasks you will provide to me? Br |
No, to get new versions of tasks worked you will need just to publish these tasks to your organization. @rizi which tasks do you interested in? |
@tatyana-kostromskaya VsBuild, MsBuild,MsTestV2, please also provide me how to do update the tasks correctly. One more question: what are the capabilities for the build agents used for? When do I need to update the build agents and when do I need to update the build tasks? Br |
List of capabilities of agents are mostly used to create demands for running pipelines by users, and as far as I know usually tasks don't relay on capabilities.
Didn't you mean VsTestV2?
Here are zip achieves with latest versions of the tasks: To update these tasks in your organization please follow the instruction:
|
In future you can build these tasks by your self. |
Thank you very much. |
Hi, do you have the timeline of when the new tasks will be installed to existing devops orgs? Regards, Thibault |
PS: I newly installed a new v2.194.0-agent with the newly released Visual Studio Enterprise 2022 and the agent did not detect capabilities for MSBuild, VSTest and VisualStudio |
PPS: Sorry just found #3569 , will follow there. But let us know if you have any timeline. |
I've blogged a few alternatives to self-building the tasks including an option to download them straight from an active Azure DevOps organization: https://jessehouwing.net/adding-visual-studio-2022-to-azure-devops-server-2020/
|
Agent Version and Platform
2.193.1, I downloaded this version from your github repository and installed it on our self hosted (on premises) azure devops server (17.143.28621.4 (AzureDevOps2019) on windows.
Visual Studio 2022 Enterprise RC has been installed before I installed the new agent.
We are using "classic builds" (not yaml builds) and all tasks (like visual studio build task or visual studio test task) still using VS 2019 instead of VS 2022.
We are selected 'latest version' in the visual studio build task, but that does not have any effect.
Settings --> Agent pools --> Default --> I see the new installed agent (2.193.1), but under capabilities it still only shows VS 2019 and MSBuild 16.
I would expected that under capabilities VS 2022 and MSBuild 17 should be listed as well?
Can you point me in the right direction to make our azure devops server/pipeline agent use VS 2022 instead of VS 2019?
This seems to be related: microsoft/azure-pipelines-tasks#15051 (comment)
br
The text was updated successfully, but these errors were encountered: