Note. . First of all, you can do all this with the community version and TFS Express 2015 on your own server (up to 5 users for free) - so donβt worry about the need to use the online version of VS or pay for VS Professional.
It is very easy to misinterpret the error message and go on a wild goose chase, trying to debug it.
Unfortunately, the message itself is simply poorly worded and that is the real problem.
Here is what such an error message really means:
"The agent cannot be found with the following capabilities: msbuild, visualstudio, vstest. In fact, I actually did not find any build agents configured for the selected build queue."
So, you think this does not apply to you because you just created the build agent?
Well, maybe you did it, but here, what probably happened:
- You created a new pool (for no reason other than you thought you should)
- Then you created a queue under this pool
- You created a powershell script file to create both the agent and assumed that it was placed in the pool you created ....
- But this is not so - it is placed in the default pool, which you do not even use ...
Yeah! So what happens when you create:
- You select a queue from the drop-down menu
- TFS tries to build by looking for a pool matching this queue, and it does not find any agents in ALL, so you get a silly useless error message with red gray.
When I finally realized what happened, I simply deleted my named pool + queue and simply returned to using the default pool.
Next time I will try to pay more attention to this post during powershell configuration:
Configure this agent, which is the agent pool? (the default pool name is 'Default')
You will need to create a queue under the pool, but then your agent should start working.
If you have a script with a specific ability that is not in your agent, you can check what your agent supports in the Features tab shown here. Of course msbuild, visualstudio and vstest here msbuild, visualstudio and vstest

Simon_Weaver Nov 06 '16 at 3:58 2016-11-06 03:58
source share