有哪些工具链可用于与 C++ 的持续集成？
.NET、Java 和其他语言的持续集成工具链定义相对明确，但 C++ 市场似乎有很多多样性。
我所说的 CI“工具链”特指用于构建脚本、自动化测试、编码标准检查等的工具。C
++ 团队使用哪些 CI 工具链？
Continuous Integration toolchains for .NET, Java, and other languages are relatively well defined, but the C++ market seems to have a lot of diversity.
By CI "toolchain" I specifically mean tools for the build scripts, automated testing, coding standards checking, etc.
What are C++ teams using for CI toolchains?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
我们使用 scons 进行由中央构建服务器运行的持续集成。 一些项目迁移到 buildbot。
我现在正在研究 rake 并考虑 此博客。 Fowler 在他的持续集成文章中提到 ThoughtWorks 偶尔会使用 rake 来构建脚本。
We used scons for continuous integration run by a central build server. Some projects migrated to buildbot.
I'm now getting into rake and considering solutions as surveyed in this blog. Fowler mentions that ThoughtWorks occasionally use rake for their build scripting in his Continuous Integration article.
你好，
我们实际上在我之前签约的一个网站上遇到了这个问题。
一个人坐下来编写工具，主要是 shell 脚本，
我们只是找不到任何商业可用的东西来执行此操作，因此 Charlie 坐下来用 bash shell 脚本编写了此脚本，并且它在 HP-UX 上运行。
干杯，
抢
G'day,
We actually faced this problem at a site where I was contracting previously.
One bloke sat down and wrote tools, mainly shell scripts, to
We just couldn't find anything commercially available to do this and so Charlie sat down and wrote this in bash shell scripts and it was running on HP-UX.
cheers,
Rob
与 C++ 中的所有其他任务一样，我在持续集成方面几乎一瘸一拐。 我的设置从 Eclipse 开始。 我将其设置为为我的项目生成 make 文件。 我有 ant 脚本，它们通过在适当的 makefile 上运行“make all”或“make clean”来完成总体构建任务。 这些 ant 脚本是我的项目的一部分，当我向系统添加新的构建配置或新的部分时，我必须更新它们。 不过，情况并没有那么糟糕。
我使用 CruiseControl 来实际运行构建。 每个项目（所有项目）都有自己的 ant 脚本，用于执行构建特定任务（复制工件、处理结果），调用项目 ant 脚本来执行构建。
我必须使用 cppunit 进行测试，并使用我在某处找到的 xslt 文件处理结果。 我在每个版本上也有错误的 svn 修订标签，因为我找不到合适的 svn 标签器。 我能找到的只是半完成多年的代码和人们争论其他人做错了。
在我看来，CC 是一个即将消亡的系统，但我还没有找到更好的 C++ 系统。 话又说回来，我也觉得 C++ 是一门垂死的语言，所以也许它的意义远不止于此。
As with seemingly every other task in C++, I'm just barely limping along with continuous integration. My setup starts with Eclipse. I set it to generate make files for my projects. I have ant scripts that do the overall build tasks by running 'make all' or 'make clean' on the appropriate makefiles. These ant scripts are part of my project, and I have to update them when I add a new build configuration or a new piece to the system. It's not that bad though.
I use CruiseControl to actually run the builds. Each project (all one of them) has an ant script of its own that performs build specific tasks (copying artifacts, processing results), calling into the project ant script to do the building.
I had to use cppunit for my testing and process the results with an xslt file I found somewhere. I also have the wrong svn revision label on each build because I can't find a suitable svn labeler. All I can find is half-completed years-old code and people arguing that other people are doing it wrong.
It looks to me like CC is a dying system, but I haven't found anything better for C++. Then again, I also feel like C++ is a dying language, so maybe it's bigger than just this.
实现了 C++ 跨平台持续集成基础架构
我们使用 Parabuild http://www.viewtier.com/ products/parabuild/screenshots.htm
我们能够将各种 Win/Mac/Linux QA 工具与其集成，并且它非常易于安装和维护：在每个平台上都可以一键安装，并且 Web 界面非常易于使用便利。
在评估几个持续集成服务器时，主要问题是它们偏向 Java：另一方面，Parabuild 非常适合 C++ 跨平台开发和 QA 工作流程
We implemented our C++ cross platform continous integration infrastructure using Parabuild
http://www.viewtier.com/products/parabuild/screenshots.htm
We were able to integrate every sort of Win/Mac/Linux QA tool with it and it's really easy to install and maintain: it's one click installation on every platform and the web interface is very handy.
While evaluating several continous integration servers the main problem was that they were Java-biased: Parabuild, on the other hand, fits well in the C++ cross platform development and QA workflow
Visual Build Professional 是我最喜欢的工具，它可以将所有其他工具整合在一起。 当然，仅适用于 Windows，但它与各种类型的 Visual Studio 以及大量测试工具、源代码控制工具、问题跟踪器等集成。不过，它仅适用于 Windows。 我知道这不是整个堆栈，但它是一个开始。
Visual Build Professional is my favorite tool for pulling together all the other tools. Windows only, of course, but it integrates with all flavors of Visual Studio and a host of test tools, source controls tools, issue trackers, etc. It is windows only, though. I know that's not the entire stack, but it's a start.
另一个选择可能是buildbot。
它是用 python 编写的，但不仅仅适用于 python 应用程序。 它可以执行任何用于构建的脚本。 如果你看看他们的成功故事，就会发现语言的种类繁多。
Another option might be buildbot.
It's written in python, but is not just for python apps. It can execute any script for doing your build. If you look at their success stories, there appear to be a wide variety of languages.