与.net和svn的持续集成 [英] Continuous integration with .net and svn

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

问题描述

我们目前尚未在我们的项目中应用自动化构建和测试持续集成 。我们没有打扰到这么远,因为我们只有2个开发人员在工作,但即使有一个团队2,我仍然认为使用连续集成和确认我们的构建不破坏或测试开始是有价值的失败。

We're currently not applying the automated building and testing of continous integration in our project. We haven't bothered this far as we're only 2 developers working on it, but even with a team of 2 I still think it would be valuable to use continous integration and get a confirmation that our builds don't break or tests start failing.

我们使用.Net与C#和WPF。我们已经创建了用于构建应用程序的Python脚本 - 使用MSbuild - 并运行所有测试。我们的源是SVN。

We're using .Net with C# and WPF. We have created Python-scripts for building the application - using MSbuild - and for running all tests. Our source is in SVN.

使用此设置应用持续集成的最佳方法是什么?我们应该得到什么工具?它应该是一个不需要很多的设置。简单的程序开始和小维护是必须的。

What would be the best approach to apply continous integration with this setup? What tool should we get? It should be one which doesn't require alot of setup. Simple procedures to get started and little maintanance is a must.

推荐答案

请查看 JetBrains的TeamCity 。免费为像你这样的小团队。易于安装和最小的烦恼。 看起来不错。远远优于CruiseControl.NET。

Have a look at JetBrains' TeamCity. Free for a small team like yours. Easy to install and minimal fuss. And it looks good. Far better than CruiseControl.NET.

CruiseControl.NET也很好,但肯定需要更多的工作来设置。

CruiseControl.NET is good too, but definitely requires more work to get setup.

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

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