Azure-pipelines-agent: dotnet core system capabilities not detected in self hosted agents

Created on 6 Jun 2019  路  2Comments  路  Source: microsoft/azure-pipelines-agent

Agent Version and Platform

Version of your agent? 2.150.3

OS of the machine running the agent? Windows

Azure DevOps Type and Version

visualstudio.com

What's not working?

I have created a new VM in Azure to be used as a self-hosted agent which has .NET Core installed. I run commands to register this agent as a self-hosted agent in Azure Devops project. Everything works fine and the agent is registered.

But when I check the System Capabilities, I find that .NET Core is not registered as a system capability.

Most helpful comment

If you deprecate the capability concept, how would a build choose a build agent from the pool that is fit for the job?

All 2 comments

@RonakThakkar, the agent doesn't register .NET Core as a system capability.

We're in an ongoing process to deprecate the capability concept, so it's now up to the pipeline scripts and code to keep track of where the .NET core SDK and runtime directories are located on disk.

You can use either run the dotnet --list-sdks and dotnet --list-runtimes commands to find out where they are located, or you can install your own side-by-side copy.

If you deprecate the capability concept, how would a build choose a build agent from the pool that is fit for the job?

Was this page helpful?
0 / 5 - 0 ratings