TeamCity 与 BuildForge
我们目前正在使用 TeamCity，并由于组织需求/限制而计划转向 BuildForge。我想对 TeamCity 和 BuildForge 进行功能比较。有人可以帮我解决这个问题吗？我可以找到 BuildForge 与其他 CI 工具（例如 Hudson、CruiseControl）的比较。
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我会使用其他比较作为基线（尤其是 Hudson 的比较，它会非常接近），并基本上创建一个您关心的功能矩阵，并查看哪些工具可以做什么。您可以向 IBM 询问他们的故障。
CI 工具的一个重要功能列表（包含 TC 数据）是 CI 比较矩阵：
CI 功能矩阵 和 持续集成软件比较。
在 Urbancode，我们的 AnthillPro 产品与 Build Forge 直接竞争，我们对功能矩阵的看法在白皮书中 “持续集成和构建管理服务器评估指南”（需要注册）。
基本上，我认为您会发现 BF 能够处理更大的环境（可扩展性、安全性、可扩展性类型优势），而 TC 更纯粹、团队级 CI 服务器（更广泛的集成和测试趋势类型活动）。
I would use the other comparisons as a baseline (especially the Hudson one which will be quite close), and basically create a matrix of features you care about, and see which tools do what. You may ask IBM for their break-down.
A great list of features for CI tools in general (with data on TC) is the CI comparison matrix:
CI Feature Matrix and Comparison of Continuous Integration Software.
At Urbancode, our AnthillPro product competes pretty directly against Build Forge, our take on a feature matrix is in a white-paper "Continuous Integration and Build Management Server Evaluation Guide" (registration required).
Basically, I think you'll find that BF is capable of handling a larger environment (scalability, security, scalability type strengths) while TC is more of pure, team level CI server (wider range of integrations, and test trending type activities).
我已经使用 BuildForge，实际上我将它与 ClearCase、ClearQuest 一起使用了十多年，今天我仍然必须在一个客户端上使用它。我的经验是：忘记IBM，来到新时代。这是 Git、JIRA、Jenkins、artifactory 的世界。我见过 TeamCity，但用得不多。这是我听说过的唯一比 Jenkins 更好的构建工具。
忘掉 BuildForge吧，它老旧、缓慢、难以使用。与 Jenkins 等具有无穷无尽插件的工具相比，BF 只是一个 shell，什么也不提供，所以你必须自己编写所有内容，并且用 Perl 编写。与 Groovy 相比，有多少年轻开发人员不能用 Perl 编写代码？将 BF 与 Jenkins 进行比较就像将 C 语言与 Java 进行比较。
举个我这些天在做的事情的例子：将一个BF实例移到另一台服务器上。对于 Jenkins 来说，它只是一个目录的副本。在BF中，你需要花一周的时间来弄清楚。
I've used BuildForge, actually I used it together with ClearCase, ClearQuest, for more than a decade and today I still have to use it at one client. My experience is: forget about IBM, come to the new age. It's Git, JIRA, Jenkins, artifactory's world. I've seen TeamCity but didn't use a lot. This is the only build tool I heard better than Jenkins somehow.
Forget about BuildForge, it's old, slow, hard to use. Comparing to tools like Jenkins has endless plugins, BF is just a shell provides nothing so you will have to write everything yourself, and in Perl. How many young developers can't write in Perl, comparing to Groovy? Comparing BF to Jenkins is like comparing C language to Java.
Give an example on what I am doing these days: move a BF instance to another server. For Jenkins, it's just a copy of a directory. In BF, you need to spend a week to figure out.