多平台开发的最佳持续集成设置
对于在多个环境中编码的开发部门来说，最佳的持续集成设置是什么？
在我的公司，我们用 C# 编写一些代码，用 Java 编写一些代码，我以前使用过 CC.Net，但从未使用 Java 编写过 CInt。
我知道 Continuum，最近也听说过 Hudson，但我从未使用过。
是对每个平台使用两个 CInt 服务更好，还是对两个平台使用同一个服务更好？
What is the best continuous integration setup for a Devleopment department that codes in multiple environments?
At my company we write some code in C# and some in Java, I've previously used CC.Net but I've never done CInt with Java.
I'm aware of Continuum and was recently told about Hudson, but I've never used either.
Would it be better to use two CInt services one for each platform or to use a single one for both?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
您为什么不尝试 JetBrains 的Team City？ 它适用于 Java 和 C#，专业版最多可免费提供 20 个用户帐户和 3 个构建代理。
Why don't you try Team City from JetBrains? It is both for Java and C# and Professional version is free up to 20 user accounts and 3 build agents.
您可以简单地使用 CruiseControl 的 Java 版本并进行两种设置。
You could simply use the Java version of CruiseControl and have two setups.
正如您已经知道如何使用 CC.Net 一样，CC.NET 可以运行任何输出 XML 的构建任务。 为什么不直接将 CC.NET 与 ant 一起用于您的 Java 代码和 C# 代码。
或者您需要在非 Windows 机器上构建吗？ CC.NET 可能适用于单声道，我还没有检查过。
请记住，任何编译所有代码并运行单元测试的持续集成设置都会为您带来巨大的好处。 在大多数项目中，与有效的持续集成设置相比，完美的设置只会带来较小的改进。 因此，我会选择您满意的东西并立即开始使用。
As you already know how to use CC.Net and CC.NET can run any build task that outputs XML. Why not just use CC.NET with ant for your java code as well as your C# code.
Or do you need to build on none Windows machine? CC.NET may work with mono, I have not checked.
Remember that any continuous integration setup that compiles all your code and run your unit tests give you great benefits. On most projects having the perfect setup only give a smaller improvement over having a continuous integration setup that works. So I would just pick something you are happy with and start using it now.
恕我直言，对您计划部署的所有平台使用一个 CI 几乎总是更好 - 这样更容易解决问题。
无耻插件：尝试来自 Bamboo，CI 服务器 .com" rel="nofollow noreferrer">Atlassian。 它一键安装，内置对 Ant 和 Maven 的支持，并且适用于所有带有 JVM 的平台。 它还可以在不同平台上进行分布式构建。
它还与 Atlassian Jira 问题跟踪器 和 鱼眼代码存储库浏览器（如果您有这些产品）。
Imho, its almost alway better to use one CI for all platforms you plan to deploy to - easier to sort out problems that way.
shameless plug: try Bamboo, the CI server from Atlassian. Its one click setup, built-in support for Ant and Maven and works on all platforms with JVM. It can also do distributed builds on different platforms.
It also integrates with Atlassian Jira Issues Tracker and Fisheye Code Repository Browser if you have those products.
哈德逊。 我已将它用于 .NET 和 Java 项目，并且让两个平台使用相同的持续集成服务器效果很好。
Hudson. I've used it for both .NET and Java projects and it works well to have both platforms using the same continuous integration server.
请注意，这假设您想要在多个平台上构建相同的代码。 硬件变得越来越便宜，因此使用虚拟机或多个物理服务器，我会选择虚拟机，只购买一台功能强大的服务器来运行它们，但如果您有很多旧的中档硬件，这可能是一个更便宜的选择。 在一台服务器上设置主源代码控制存储库，并使用要为其构建的客户端操作系统设置服务器。 例如，拥有一个包含您选择的操作系统的 svn 服务器、一个用于进行 Linux 构建的 Linux 服务器和一个用于进行 Windows 构建的 Windows 服务器。 然后只需安装最适合给定代码库和操作系统的持续集成软件即可。
Note this assumes you want to build the same code on multiple platforms. Hardware has gotten cheaper so use virtual machines or multiple physical servers I'd go with virtual machines and just buy one powerful server to run them on but if you have a lot of old mid range hardware that may be a cheaper option. Set up a main source control repository on one server, and set up servers with the client operating systems you want to build for. For example have a svn server containing your operating system of choice, a Linux server to do Linux builds and a Windows server to do Windows builds. Then just install what ever continuous integration software works best for the given code base and operating system.