You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please add "collection_name" field in which the agent pool is created. Now this info is missing in .agent file and in case of 100+ collections the agent info is almost useless as it's hard to find via REST API.
The text was updated successfully, but these errors were encountered:
Hi @kodzis-eib, thanks for the reporting! We are working on higher priority issues now, but we'll get back to this one soon
As a workaround, you could try to get the collection name from the "serverUrl" config property
@kodzis-eib Hello,
in Azure DevOps Server, agent pools are scoped to the entire server, see the following doc.
Our API documentation: Pools - Add is likely causing confusion - the /{collection}/ is not required in the URL. I will look into fixing the API docs.
I am not sure if this solves your problem, but you can check whether a particular AgentPool is available on project level, using the Queue APIs. Therefore, by iterating over all queues you can identify all Projects (and therefore also collections) where a given agent is available.
Please feel free to reactivate the issue in case you have any further questions!
Describe your feature request here
Please add "collection_name" field in which the agent pool is created. Now this info is missing in .agent file and in case of 100+ collections the agent info is almost useless as it's hard to find via REST API.
The text was updated successfully, but these errors were encountered: