-
Notifications
You must be signed in to change notification settings - Fork 853
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
System Capabilities do not support VS2019 #2004
Comments
Looks like all my text didn't save. Each of the above capabilities pointed to a folder location. |
@ilyas1974 do you have the agent diag log? |
Here is the build log. I don't have an agent diag as the job never actually reached the agent https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_build/results?buildId=2256106 |
@ilyas1974 are you able to logon any of those agents that installed on VS2019 box and grab agent config diag log, we trace out the capability discovery process. |
The logs can be found at \dditlabs\team\ilyas\Agent Diag\ |
@ilyas1974 i don't have permission :) |
try \ddmbldw066\a (the actually agent directory on the system). |
We haven't start looking for VS2019 capability yet. :) |
Is there a timeline for VS2019 capabilities? Preview 1 was released publicly at //Connect this week. I added these demands manually to the agent and am unblocked. Manual entry is fine for a single system, but is error prone once we start rolling out in bunk. |
@ilyas1974 we will try to get it fixed in next agent release. |
Thank you |
@TingluoHuang what is the schedule for agent releases? My team is also looking at this, as it's currently affecting moving our builds to Azure Pipelines. |
i will merge the PR and start next agent release 2.144.1 within this week. |
Thanks @TingluoHuang, I've verified a that 2.144.1 works. |
close this issue since 2.144.2 (with the fix) is in release process. |
The latest Azure DevOps Agent (2.144.0) does not seem to pull the same system capabilities for VS2019 as it does for VS2017. At this time, it does not pull all capabilities related to VS2019. The capabilities we were expecting are as follows
VisualStudio -
VisualStudio_16.0 -
VisualStudio_IDE -
VisualStudio_IDE_16.0 -
VSSDK160Install -
VSTest -
VSTest-16.0 -
The text was updated successfully, but these errors were encountered: