Using TFS 2018, I have a need to deploy (individually) different team projects to the same target server. Until update 2 is released, it is not possible to share deployment groups.
However, there must be a way to deploy different team projects to the same server.
My thought was maybe I have to create one release agent for each project, since I cannot share a deployment pool. However, I read a TechNet post from 2016 that says
It is recommended to limit the number of agents, in a build machine, to the number of CPU cores it has.
Whether the article was being ambiguous and means build - or - release agents, or only means build agents only, I don't know. OK, my target server has 4 CPUs and I need the option to deploy any number of individual, independent Team Projects to the same server, so it's starting to look like creating a separate depolyment agent per team project is not going to be feasible.
Until update 2 is released it is not possible to share the same deployment group. My question is how do I actually achieve this necessary outcome of independently deploying more than one Team Project to the same server?
Please remember that I am restricted to TFS. VSTS is not an option in my scenario.
答案 0 :(得分：2)
这个建议对于构建服务器来说真的更多。构建服务器在CPU /内存方面的要求与发布代理有很大不同。在运行构建时，构建代理程序是内存和CPU密集型的。您不会在发布代理上运行构建。
绝大多数时间，释放代理将处于空闲状态。在使用第二个代理程序安装创建第二个部署组作为解决方法之前，我没有看到问题，直到您可以升级为止。