Why is my new VSTS built using the legacy "Hosted VS2017" agent?
I just created a very simple assembly on VSTS. I used a blank template, selected the "Hosted VS2017" agent, specified the appropriate source repository, and added one task that just installs NPM. Then I enqueued it using the "Hosted VS2017" agent.
After that, he waits for an available agent, apparently indefinitely. Right above where he says "1 position in the queue" he has a "Hosted Agent" which is a link. If I click on it, I go to a page showing:
Clicking on the text "please migrate" will take me to here , but that doesn't seem to help much. It looks like using Hosted VS2017 would be the right agent.
Any ideas on how to set up my assembly correctly? I don't feel like I need to migrate anything as I am just starting from scratch.
source to share
For hosted agents (Hosted and Hosted VS2017) it is always updated to the latest version automatically. And it seems like a bug based on the screenshot you suggested. And there is a VSTS Hosted agent outdated error message , you can follow it.
The latest version of Agent.Version is 2.119.1:
source to share