在 TFS 2010 中使用多个构建代理
在我的 TFS2010 环境中，我有 2 台机器作为专用构建代理。我期望一旦注册了这些构建代理，如果我对新的构建进行排队，TFS 将等待第一个空闲代理并将该代理分配给该构建，但是如果我对一个构建进行排队并且另一个构建已经在运行，则第二个构建即使有一个构建代理什么都不做，它仍处于排队状态，直到第一个构建完成。
我没有在构建定义中设置任何标记过滤器或名称过滤器或实际上可能将构建绑定到特定服务器的任何其他内容，所以我不确定发生了什么。
为了测试两个代理都在工作这一事实，我将 CI 构建分配给一个代理，将每日构建分配给另一个代理，然后两者都转到不同的代理并正确构建，所以我不知所措......
In my TFS2010 environment, I have 2 machines as dedicated build agents. I was expecting that once these build agents were registered, if I queue a new build, TFS would wait for the first free agent and assign that agent to the build, but if I queue a build and another build is already running, the second build sits in a queued state until the first build is finished even though there is a build agent sat doing nothing.
I haven't set any tag filters or name filters or in fact anything else in the build definition which might tie the build to a particular server, so I'm not sure what's going on.
To test the fact that both agents are working, I've assigned the CI build to one agent and the daily build to another and both then go to the different agents and build correctly so I'm at a loss...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
TFS 不会将同一构建定义的另一个构建发送到同一构建控制器，因此如果您有两个构建定义，并且每个定义都有一个构建排队，那么它将同时运行这两个构建定义。
TFS won't send another build of the same build definition to the same build controller, so if you have two build definitions, and each has a build queued, it will run both at a time.