设置与SVN的连续集成 [英] Setting up Continuous Integration with SVN

问题描述

您建议使用哪些工具来设置CI以构建和部署使用SVN进行源代码控制的DotNetNuke上构建的多个网站？

What tools would you recommend for setting up CI for build and deployment of multiple websites built on DotNetNuke using SVN for source control?

我们目前正在配置Cruise Control与NAnt，NUnit，NCover和Trac配合使用作为测试用例。什么其他组合值得调查？

We are currently looking at configuring Cruise Control to work with NAnt, NUnit, NCover and Trac as a test case. What other combinations would worth investigating?

我们完全控制我们的开发环境，所以使用某种形式的CI是确定在这里，但我也想说服我们的生产服务团队

We have full control of our development environment so using some form of CI is certain here but I would also like to convince our production services team that they can reliably deploy to the system test, uat and even production environments using these tools.

推荐答案

我们使用CruiseControl和NUnit，它们可以使用这些工具可靠地部署到系统测试，甚至生产环境。 NCover，FxCop，SVN和一些我们自己编写的自定义工具来生成报告。在我看来，它证明了（在过去几年）是一个很好的组合。

We use CruiseControl with NUnit, NCover, FxCop, SVN and some custom tools we wrote ourselves to produce the reports. In my opinion it has proven (over the last few years) to be an excellent combination.

令人沮丧的是，MS限制了工具到VSTS。它的测试框架和NUnit一样好，但你不能使用它的代码覆盖工具或其他任何东西。

It's frustrating that MS restricts all of its integration tools to VSTS. Its test framework is as good as NUnit, but you can't use its code coverage tools or anything else.

我会看看XNuit - 看起来很有前途但目前缺少UI）。

I'd check out XNuit - it's looking pretty promising (but currently lacking UI).

我们自动化夜间构建，您可以自动化UAT和手动测试构建，但我不确定我们是否想自动化发布到我们的生产服务器。即使是任何改变也是足够重要的，有人不得不观看它。

We automate nightly builds, and you could automate UAT and manual test builds, but I'm not sure that we'd ever want to automate the release to our production servers. Even if it were any change would be important enough that someone would have to watch over it anyway.

这篇关于设置与SVN的连续集成的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！