关于持续集成系统的建议
我们目前正在评估与 Visual Studio 2008 (C#) 和 Subversion 交互的不同应用程序，以自动构建我们的核心库。 我们希望每晚执行构建，并通过电子邮件将所做的更改列表发送给每个开发人员，或者将最新版本推送到每个工作站。 您对这些工具的使用体验如何？有哪些建议？
推荐软件
推荐文章
We are currently evaluating different applications that interface with Visual Studio 2008 (C#) and Subversion to do automated builds of our core libraries. We are hoping to have nightly builds performed and either email the list of changes made to each developer or have the latest versions be pushed to each workstation. What has been your experience with these tools and what are some recommendations?
Suggested software
Suggested articles
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（9）
如果您使用 trac 进行问题跟踪，则 bitten 插件效果很好。 它不是特定于平台的（我们在工作中在 Windows 和 Linux 上运行它，分别使用 msbuild/mstest 和 make/gcc/cpptest）。
If you are using trac for issue tracking, the bitten plug-in works well. It's not platform specific (we run it on both Windows and Linux at work, with msbuild/mstest and make/gcc/cpptest respectively).
我正在使用 hudsons Jenkins 进行日常构建。 它确实非常容易设置和维护。 而且它有很多插件完全可以满足我们的要求。
I am using hudsons Jenkins for getting daily build. It really very easy to setup and maintain. And it have a lot of plugins which full fill our requirements.
有关使用 cc.net 和 msbuild 的一些花絮。 如果您正在构建 C/C+= 项目，那么 msbuild 至少在 VS 2005（也许更早的版本）中是不可靠的。 我没有用 VS 2008 进行测试。我们发现有时 msbuild 可以正常工作，有时则不能。 在尝试解决该问题时，我们发现 vcbuild.exe 在构建 C/C++ 解决方案时似乎可以很好地代替 msbuild。
A couple of tidbits about working with cc.net and msbuild. If you are building C/C+= projects, msbuild is, um, unreliable at least with VS 2005 (and perhaps earlier). I have not tested with VS 2008. We found that sometimes msbuild would work properly, sometimes not. In trying to solve the problem, we found vcbuild.exe which seems to work well in place of msbuild when building C/C++ solutions.
Cruise Control.net (ccnet) 可以满足您所需的一切。 它非常容易使用，只需确保您是否要将其作为服务运行，您给它一个帐户并且不要让它作为网络服务运行，这样您就可以授予它在内联网盒子上的权限并让它执行xcopy 部署。
它具有各种电子邮件模式，失败时、全部时、失败后修复等等。
Cruise Control.net (ccnet) does everything you are looking for. Its pretty easy to use, just make sure if you are going to run it as a service, you give it an account and don't make it run as network service, that way you can give it rights on intranet boxes and have it do xcopy deploys.
It has all kinds of email modes, on failure, on all, on fix after failure, and many many more.
Hudson 是我见过的最简单的持续集成/每日构建工具。 不确定它是否满足您的所有要求。
Hudson is the easiest continuous-integration / daily-build tool I've seen. Not sure if it meets all your requirements.
看看 JetBrain（ReSharper 背后的人员）TeamCity
Take a look at the JetBrain's (guys behind ReSharper) TeamCity
我已将 cc.net 与 nant 和msbuild 取得了巨大成功，强烈推荐它。
I've used cc.net with nant and msbuild with great success, would highly recommend it.
在我的上一个雇主那里，我使用 cc.net 设置了一个构建服务器。 预计至少需要一两天的时间来完成设置。 我将 cc.net 与 nant 和 msbuild 一起使用。 这些项目在功能上有很多重叠，因此考虑一下您想要如何设置一切可能是个好主意。
我最终解决的设置是在服务器上使用 cc.net 从 subversion 检索项目并启动 nant 脚本。 nant 用于调用 msbuild 来构建 Visual Studio .sln 文件并执行所有其他构建步骤，例如运行测试等。
我也快速浏览了 teamcity。 乍一看它比 cc.net 好很多，但我还没有时间尝试。 这当然值得一看。
At my last employer I set up a buildserver with cc.net. Expect at least one or two days work to set it up. I used cc.net together with nant and msbuild. These projects have a lot of overlap in functionality so it might be a good idea to think about how you want to set everything up.
The setup I eventually settled with was cc.net on the server to retrieve the project from subversion and fire off the nant scripts. nant was used to call msbuild to build the visual studio .sln files and do all the other build steps like running tests etc.
I had a quick look at teamcity too. On first sight it looks a lot better than cc.net but I didn't have time to try it out yet. It's certainly worth checking out.
我使用 CC.Net 以及 SubVersion 和 MSBuild 来完成此任务。 这是一个很好的实现指南，我发现它非常有帮助。
I use CC.Net along with SubVersion and MSBuild to accomplish this. Here is a great guide for implementing this which I followed on found very helpful.