blocks|key|3460072|text|可能取决于您的进程。如果你有覆盖你的代码的单元测试，那么持续集成是值得的。我假设你们都在一个单一的工作模块上工作，因为项目需要2-3周。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3460073|我不认为人们会为他们的每一次提交运行每一个测试，持续集成在这里有很大的帮助。|3460074|另一个原因是如果你的项目是高度模块化的。我曾经在有很多模块的系统中工作，开发人员在提交之前不会对整个网站进行功能测试。因为开发人员没有签出完整的代码，所以其他模块甚至不会构建，所以事情甚至可能无法正确编译。|3460075|无论如何，我都会推荐持续集成。有了像Hudson和Cruisecontrol这样的设置，它不需要花很多时间来设置，并且很快就能收回成本。|3460076|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

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.

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.

blocks|key|3460159|text|就我个人而言，我认为CI和它鼓励的各种过程总是有用的。一旦服务器自行设置好，获取CI设置就相当简单了。基本上，您只是从一个项目复制一个配置文件，对其进行编辑，然后创建一个新项目。我不会因为“建立每个项目的努力”而不使用CI。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3460160|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Personally, I think CI and the various processes it encourages are always useful. Getting CI setup is rather trivial once you have the server set up itself. You're basically just copying a configuration file from one project, editing it, and creating a new project. I wouldn't not use CI because of the "effort of setting up each and every project".

blocks|key|989103|text|持续集成不仅是一个工具问题，而且是一套流程(定期提交，有一个版本控制系统……)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|989104|关于I.C软件，您可以在不到10分钟内安装、配置并开始使用Hudson！那么为什么你不使用任何IC系统呢？|offset|length|989105|entityMap|0|LINK|mutability|MUTABLE|url|http://hudson-ci.org/^0|0|T|6|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Continuous Integration is not only a tool matter, but also a set processes (commit regularly, have a version control system...).

Concerning the I.C software, you can install, configure and start to use <a href="http://hudson-ci.org/" rel="nofollow noreferrer">Hudson</a> in less than 10 minutes! So why would you go without any IC system?

blocks|key|4307419|text|这实际上取决于您可以多快地设置自动构建，然后将其连接到CI服务器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4307420|.NET|offset|length|style|BOLD|4307421|我看到我们使用UppercuT在几分钟内完成了一个项目从无自动化构建到自动化构建。我们使用它和CruiseControl.NET+(在配置中，我们利用预处理器为每个项目b/c添加一行)。|4307422|http://code.google.com/p/uppercut/|4307423|这里有一些很好的解释：UppercuT|4307424|entityMap|0|LINK|mutability|MUTABLE|url|1|http://ferventcoder.com/category/uppercut.aspx^0|0|0|4|0|0|0|Y|0|0|B|8|1|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|L|3|M|5|6|7|15|8|@]|9|@$D|16|E|17|1|18]]|A|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|K]]|U|$5|Q|R|S|A|$T|V]]]]

It really depends on how fast you can set up an automated build and then get that hooked up to a CI server.

.NET

I've seen us go from no automated build to an automated build for a project in a few minutes using UppercuT. We use that and CruiseControl.NET (in the configuration, we add a line per project b/c we take advantage of the preprocessor).

<a href="http://code.google.com/p/uppercut/" rel="nofollow noreferrer">http://code.google.com/p/uppercut/</a>

Some good explanations here: <a href="http://ferventcoder.com/category/uppercut.aspx" rel="nofollow noreferrer">UppercuT</a>

blocks|key|4307283|text|如果您的许多应用程序共享任何公共组件或模块，CI和测试可能会帮助您注意到一些故障。如果它们真的都是一些丢弃的、自包含的脚本，那么您可能不需要CI，但这是一个艰难的决定。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4307284|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If your many apps share any common components or modules, CI and tests will likely help you notice something breaking. If they are really all little throw away, self contained scripts then you might not need CI, but it's a tough call.

blocks|key|989175|text|正如其他人所指出的，一旦CI设置好了，那么添加一个新项目就很简单了，所以我会说去做吧。你将看到的一个好处是，如果你的任何项目发生了变化，你已经有了CI，希望你的单元测试已经准备好了，这样你就不会得到任何令人讨厌的惊喜了！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|989176|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

As others have pointed out, once CI is setup then adding a new project is trivial so I'd say go for it. One benefit you're going to see is that if any of your projects do ever change you've already got CI and hopefully your unit tests ready to go so you won't get any nasty surprises!

blocks|key|3460319|text|持续集成不仅确保了stuff的工作，还允许您记录和测试发布过程，就像一个新开发人员所做的那样。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3460320|这确保了客户得到的是经过测试的内容，而不是开发人员从硬盘中拼凑出来的内容。|3460321|这对于维护来说可能是非常重要的。|3460322|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Continous Integration is not only ensuring stuff works, it also allows you to DOCUMENT and TEST the release process as it would be done by a new developer.

This ensures that the customer gets what has been tested, not what the developer just throws together from his harddisk.

This may be extremely important for maintainance purposes.

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.

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?

Is continuous integration worth it for small projects?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

自从我5个月前加入公司以来，我一直在推动公司的持续集成，但在看到我们工作的应用程序类型后，我开始认为可能不值得为持续集成建立每个项目的努力。如果你在一个开发部门工作，项目平均需要2-3周，一旦部署，你很少担心它，持续集成值得设置它的麻烦吗？

问对于小项目来说，持续集成值得吗？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对于小项目来说，持续集成值得吗？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对于小项目来说，持续集成值得吗？
EN