持续集成是否值得为小项目？ [英] 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屋！