TeamCity 与 FinalBuilder Pro 的持续集成服务器对比
我见过很多 TeamCity 与 CCNet 的比较，但很少看到 TeamCity 与 FinalBuilder Pro 的 CI 的比较。
请原谅我不是在比较苹果与苹果，我熟悉 TeamCity，但是我工作的公司已经购买了包含 CI 服务器的 FinalBuilder Pro。
希望得到一些比较，意见。如果 TeamCity 不提供高于 FinalBuilder 的更多功能，我们不希望必须支持两个系统。
提前致谢。
I have seen lots of comparisons for TeamCity vs CCNet, but not much for TeamCity vs FinalBuilder Pro's CI.
Forgive me if I am not comparing apples to apples, I am familiar with TeamCity however the company I work for has already purchased FinalBuilder Pro which has a CI Server included.
I'm hoping to get some comparisons, opinions. If TeamCity does not offer more above FinalBuilder we do not want to have to support two systems.
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
以下是 TeamCity 中存在但 FinalBuilder 中不太可能存在的一些功能：
针对 Java 和 .NET 的集成代码覆盖率和重复项查找器
FinalBuilder 支持某些 VCS 系统，但 TeamCity 不支持这些系统。
免责声明：我是 TeamCity 开发人员之一。
Here are some features present in TeamCity and unlikely present in FinalBuilder:
Integrated code coverage and duplicates finder for Java and .NET
FinalBuilder has support of some VCS systems, which are not supported by TeamCity, though.
Disclaimer: I'm one of TeamCity developers.
我们使用 TeamCity 进行构建编排，但使用 FinalBuilder 来实际执行单独的构建。
我喜欢 FinalBuilder，因为它易于编写脚本和可维护性，但我也喜欢 TeamCity，因为 KIR 回答中的所有要点。
在我们的设置中，每个 TeamCity buildconfig 都配置为使用命令行运行程序，并使用要运行的脚本的名称调用 Finalbuilder 的 fbcmd.exe。
所有的甜蜜和光明。
We are using TeamCity for the build orchestration, but using FinalBuilder to actually carry out the individual builds.
I love FinalBuilder for the ease of scripting and maintainability, but I also love TeamCity for all the points in KIR's answer.
In our setup, each TeamCity buildconfig is configured to use the commandline runner, and finalbuilder's fbcmd.exe is invoked with the name of a script to run.
All sweetness and light.
我在英国的一次持续集成演讲中对这两种产品进行了比较 - 基本上我的发现是 TeamCity 使用起来更直观。在我看来，FinalBuilder 的语言含糊不清，而且设置构建似乎很笨拙。
工作完成后，它是一个非常好的系统 - 但对我来说，TeamCity 比 Final Builder 更直观，并且具有更好的用户体验
。虽然非常主观——每个工具都非常好。这取决于您对什么感到满意，而我对 TeamCity 感到更满意
I have done a comparison of the 2 products for a continuous integration talk in the Uk - basically my findings were that TeamCity was more intuitive to use. FinalBuilder seemed to me to be ambigious in its language and seemed to be clunky to set up builds
Once the work was done it was a very good system - but for me TeamCity was much more intuitive and had a better user experience than Final Builder
this is very subjective though - each tool is very good. It comes down to what you are comfortable with and I was much more comfortable with TeamCity