线程在运行完成时结束？(Threads ends when run finish? [duplicate])

 我不认为这是可能的。 一个控制器可以平衡一个可用代理的构建，并且与构建的代理模式相匹配（如构建定义中定义的）。 除非你有大量的构建，否则我会坚持使用每个集合的单个控制器和更多的代理。 与代理（编译，测试和部署）相比，控制器的工作量非常小。 
 
 
 对于你的情况，我会尝试像这样： 
 
 调节器 
 
 
 
 门控代理1（在\\ sv-BuildAgent1上） 
 
 
 门控代理2（在\\ sv-BuildAgent2上） 
 
 
 QA Agent ...（在\\ sv-BuildAgent3上） 
 
 
 其他代理商...（在\\无论何地） 
 
 
 ...等等... 
 
 
 现在，每个Gated Build's Definition都会将Build Agent设置为“ Gated Agent * ”（位于3.高级 - > 代理设置 - > 名称过滤器中的进程选项卡下）。 现在将选择以“门控代理”开头的任何代理。 您可以根据需要轻松地将其扩展到尽可能多的代理商。 
 
 编辑： 
 
 您还可以将代码上的代码放到一个类似的结果。 这可能更容易配置。 您可以在构建代理的属性中定义标记，并配置定义以在名称过滤器（上面）的相同部分中使用它们。 

I don't think this is possible. A controller can balance a build out onto which ever agents are available and that match the agent pattern of the the build (as defined in the build definition). Unless you have a serious load of build's, I would stick with a single controller per collection and more agents. The controller does very little work compared to and agent (which does the compilation, testing and deployment).
 
 
For your cases I would try something like:
 
Controller
 
 
 
Gated Agent 1 (on \\sv-BuildAgent1)
 
 
Gated Agent 2 (on \\sv-BuildAgent2)
 
 
QA Agent... (on \\sv-BuildAgent3)
 
 
Other agents... (on \\wherever)
 
 
...etc...
 
 
Now each of the Gated Build's Definition you would set the Build Agent to "Gated Agent *" (It's under the Process tab in 3. Advanced -> Agent Settings -> Name Filter.). This will now pick any agent that starts with "Gated Agent". You can easily scale this to as many agents on as many boxes as you need.
 
EDIT:
 
You can also put Tags on Build Agent to a achieve a similar result. This may be easier to configure. You Define the Tags in the Build Agent's properties and Configure Definitions to use them in the same section as the Name Filter (above).