多个构建代理 - TeamCity - VisualSVN 服务器 - ASP.Net
我正在考虑使用 2 个构建代理来设置 TeamCity。其中一个是我们的临时服务器，它将是我们开发版本的精确副本，并在每次 SVN/GIT 提交时更新。另一个是我们的实时服务器，它只会手动更新，不会复制某些文件（例如 web.config）。
这个设置可以吗？我之前曾使用 CCNet 和 MSBuild 的组合来完成此操作，但它非常繁琐。
在 TeamCity 的标准版本上，您可以有 20 个集成，即 20 个活动集成（可以关闭旧集成，或者我需要删除旧集成并在需要时重新添加它们）。
最后，我一直是一个 SVN 人，但我听说并看到人们越来越多地使用 GIT，它是否更好，或者我可以继续使用 SVN。
提前干杯。
I am thinking about setting up TeamCity with 2 build agents. One being our staging server with will be an exact copy of our development version and updated on every SVN/GIT commit. And the other would be our live server which would only update manually and wouldn't copy over certain files (web.config for example).
Is this setup possible? I have done this before using a combination of CCNet and MSBuild, but it was very fiddly.
On the standard version of TeamCity you can have 20 integrations, is that 20 active integrations (old ones can be switched off or would I need to delete the old ones and re-add them if needed).
And finally I have always been an SVN man, but I hear about and see people using GIT more and more, is it any better or am I fine just carrying on with SVN.
Cheers in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
对于这种情况，您不需要更多代理。您所需要的只是更多构建配置。第一个将部署在由每次提交触发的登台服务器上，第二个将通过按钮部署在生产环境上。
You don't need more agents for this scenario. All you need is more build configurations. One will deploy on your staging server triggered by each commit and second to deploy on your production environment on push button.
是的，TeamCity 确实可以实现这一点。如果您已使用 CC.NET 和 MSBuild 完成此操作，则从 TeamCity 调用 MSBuild 脚本应该很简单。 TeamCity 开箱即用地支持 MSBuild。顺便说一句，JetBrains 使用的术语是“配置”。 “构建代理”用于支持多个/同时构建。
对于有关 SVN 与 Git 的问题，请进行搜索，您会找到大量资源，但这里有一些亮点：
Yes, this is certainly possible with TeamCity. If you've already done this with CC.NET and MSBuild, it should be straightforward to call your MSBuild script from TeamCity. TeamCity supports MSBuild out of the box. BTW, the term that JetBrains uses for what you are talking about is "configurations". "Build agents" are for supporting multiple/simultaneous builds.
For your question regarding SVN vs Git, do a search and you'll find plenty of resources, but here are a few highlights: