关于持续集成系统的建议 [英] Recommendations regarding Continuous Integration systems
问题描述
我们目前正在评估与Visual Studio 2008（C＃）和Subversion接口的不同应用程序，以自动构建我们的核心库。我们希望每晚执行构建，并通过电子邮件发送给每个开发人员的更改列表或将最新版本推送到每个工作站。
建议的软件
/ p>建议的文章
- a href =http://dotnet.org.za/cjlotz/archive/2008/01/15/continuous-integration-from-theory-to-practice-2nd-edition.aspx =nofollow noreferrer>连续整合：从理论到实践第2版（CC.net）
- 使用Hudson自动化您的ASP.NET构建和部署过程
<
Cruise Control.net（ccnet）执行你所寻找的一切。它很容易使用，只是确保如果你要运行它作为一个服务，你给它一个帐户，不要让它作为网络服务运行，这样你就可以赋予它在内部网箱的权利，并有它做xcopy部署。
它有各种电子邮件模式，失败时，失败后修复等等。
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
- Continuous Integration: From Theory to Practice 2nd Edition (CC.net)
- Automating Your ASP.NET Build and Deploy Process with Hudson
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.
这篇关于关于持续集成系统的建议的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
