对于小项目来说，持续集成值得吗? [英] Is continuous integration worth it for small projects?

问题描述

自从我 5 个月前加入以来，我一直在推动我的公司进行持续集成，但是在看到我们正在处理的应用程序类型后，我开始认为可能不值得花费精力来设置每个应用程序和持续集成的每个项目.

I've been pushing for continuous integration at my company since I joined 5 months ago, but having seen the type of applications we work on I'm starting to think that it might not be worth the effort of setting up each and every project for continuous integration.

如果您在一个开发部门工作，那里的项目平均需要 2-3 周时间，而且一旦部署，您就很少需要担心它，持续集成值得设置它的麻烦吗?

If you work in a development department where the average project takes 2-3 weeks and once it's deployed you seldom if ever have to worry about it, is continuous integration worth the hassle of setting it up?

推荐答案

可能取决于您的流程.如果您有涵盖代码的单元测试，那么持续集成是值得的.我假设你们都在一个单一的工作模块上工作，因为这些项目是 2-3 周.

Probably depends on your process. If you have unit tests that cover your code, then continuous integration is worth every bit. I'm assuming that you guys all work on a single module of work as the projects are 2-3 weeks.

我认为人们不会为他们的每一个提交都运行每一个测试，持续集成在这里有很大帮助.

I don't think folks will run every test for every one of their commits and continuous integration helps a lot here.

另一个原因是您的项目高度模块化.我曾在有很多模块的系统中工作过，开发人员在提交之前不会对整个网站进行功能测试.事情甚至可能无法正确编译，因为其他模块甚至无法构建，因为开发人员没有检查完整的代码.

The other reason would be if your project is highly modularized. I've worked in systems where there are lots of modules and a developer wouldn't be functional-testing the entire website before committing. Things might not even compile properly as the other module wouldn't even build because the developer did not checkout the complete code.

无论如何我都推荐持续集成.借助 Hudson 和 Cruisecontrol 等设置，无需花费大量时间即可进行设置并快速收回成本.

I'd recommend continuous integration anyway. With setups like Hudson and Cruisecontrol, it doesn't take a lot of time to set up and pays for itself quickly.

这篇关于对于小项目来说，持续集成值得吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！