We are using VSTS to build a typical ASP.NET MVC web application. It had previously been working on hosted build agents, and they currently work on local agents.
We are trying to get them to use hosted Visual Studio 2017 build agents, so we don't rely on developers' laptops, and even bought additional build minutes. However, when I try to queue a build against the hosted Visual Studio 2017 agent queue, I get the following error:
No registered agents found in the selected queue with the following capabilities: azureps, npm, yarn, node.js, msbuild, visualstudio, vstest, sqlpackage
These hosted agents should have all of those and when I look in the capabilities of the agent queue, it appears to have everything yet it still will not build. If I tell it to queue anyway, the build fails, saying:
No registered agents found in the selected queue with the following capabilities: azureps, npm, yarn, node.js, msbuild, visualstudio, vstest, sqlpackage. Use a different queue. More information.
The build works great against our local agent queue running on our laptops. What could be blocking the hosted agents?
