问题描述
.NET，Java和其他语言的持续集成工具链相对定义清晰，但C ++市场似乎有很多的多样性。
通过CItoolchain我特指用于构建脚本，自动测试，编码标准检查等工具。
我们使用Parabuild实现了我们的C ++跨平台连续集成基础设施
p>
我们能够集成所有类型的Win / Mac / Linux QA工具，它非常容易安装和维护：在每个平台上的单击安装和Web界面非常方便。
在评估几个连续集成服务器时，主要的问题是他们是Java偏执：Parabuild，在另一方面，非常适合C ++跨平台开发和QA工作流程
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?
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
这篇关于存在哪些工具链用于与C ++的持续集成？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！