持续集成与南特 [英] Continuous Integration with Nant

查看:171
本文介绍了持续集成与南特的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我是preparing使用持续集成的第一次。我将使用南特的自动化构建,测试任务,并想找到合适的CI工具来查询资料库并执行脚本南特

I am preparing to use continuous integration for the first time. I will be using Nant for the automated build and testing tasks, and am trying to find the appropriate CI tool to poll the repository and execute the Nant script.

我迄今松散研究以下内容:

I have so far loosely researched the following:


  • 哈德森

  • 巡航控制

  • 德拉科

我的感觉到目前为止是,由于大部分工作将在南特完成,德拉科,因为它被认为是易于安装/设置就可以了。巡航控制和哈德森,在另一方面可能会提供更好的报告选项。

My sense so far is that since most of the work will be done by Nant, Draco would be fine because it is supposed to be easy to install/setup. Cruise Control and Hudson, on the other hand might provide better reporting options.

什么是使用南特的构建和测试任务时进行持续集成的最佳方式?

What is the best way to perform Continuous Integration when using Nant for the build and test tasks?

推荐答案

我们使用 CruiseControl.NET 作为我们的CI与我们全力打造系统,恶性为沿服务器。它一直非常好,在过去5年。我因为看着其他的替代品,并一直没能找到任何令人信服的理由(S)切换。

We use CruiseControl.NET as our CI server along with our full build system being in NAnt. It has worked exceptionally well over the past 5 years. I've since looked into other alternatives and have not been able to find any compelling reason(s) to switch.

CruiseControl.NET有不同的源代码控制系统惊人的支持。另外,我喜欢他们的应用程序是如何扩展的,因为我们已经建立了集成到它的几个系统。

CruiseControl.NET has amazing support for different source control systems. Also, I enjoy how extensible their application is as we've built a few systems that integrate into it.

这篇关于持续集成与南特的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆