blocks|key|4299675|text|到目前为止，This是我读过的最好的解释。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4299676|entityMap|0|LINK|mutability|MUTABLE|url|http://martinfowler.com/articles/continuousIntegration.html^0|6|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://martinfowler.com/articles/continuousIntegration.html" rel="noreferrer">This</a> is by far the best explanation I have read so far.

blocks|key|235420|text|最简单地说，它只是一种机制，每当签入到某个修订控制系统(CVS等)中时，它都会重新构建您的项目。但是，这可以扩展到包括运行测试，一直到生成CD映像、在VM中挂载它、安装产品并在其上运行完整测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|235421|它有一个简单的优点，即在代码更改尽可能早地中断系统时突出显示。它不仅可以检测代码中的中断，还可以突出显示是谁造成了中断。这种心理效应非常有效地鼓励在签入之前进行良好的测试！|235422|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

At its simplest, it is simply a mechanism that rebuilds your project whenever a check in is made into some revision control system (CVS etc). This can be extended though to include running tests, all the way through to generating a CD image, mounting it within VMs, installing the product and running full tests on it.

It has the simple advantage of highlighting when code changes break the system as early as possible. Not only does it detect breaks in the code, it highlights who caused the break. This psychological effect is very effective in encouraging good testing prior to check in!

blocks|key|3452826|text|它是一种实践，它确保软件开发过程的所有方面都排列在一起，以允许每天创建产品的工作版本。它作为极限编程的一部分而广为人知。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3452827|这涉及到构建自动化、自动化测试、日常签入、使用源代码存储库等，但最终目标是帮助整个项目根据核心敏捷原则运行，以便您尽早且频繁地交付。反过来，这可以帮助你利用来自用户的反馈，等等。|3452828|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It is the practice of ensuring that all aspects of your software development process are lined up to permit the daily creation of a working version of your product. It is best known as part of Extreme Programming.

This involves things as far afield as build automation, automated testing, daily check-ins, using a source code repository, etc. But the ultimate goal is to help the entire project run according to core Agile Principles so that you deliver early and often. This, in turn, helps you leverage feedback from your users, etc.

blocks|key|3452929|text|%2B1表示指向Fowler页面的链接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3452930|就我个人而言，我只是发现知道什么时候没有编译是很好的，因为我们有一个单一构建的糟糕实践(是的，我们是在生产构建上开发的；我们很棒)。在我离开之前，我们还没有得到集成测试阶段。|3452931|然而，过了一段时间后，它确实减少了大量的代码更改(与当时盛行的“签入并祈祷我的更改不要冲突”相比)。最终，大多数开发人员开始频繁地进行小更改，只是为了从CC.Net任务栏图标获得确认。|3452932|总体而言，我感到非常欣慰的是，如果有必要，我们可以立即发送一个构建版本。如果我们只集成了几个烟雾测试，我认为压力水平会大大降低。|3452933|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|$]]

+1 for the link to Fowler's page.

Personally, I just found it "nice" to know whenever something didn't compile because we had the poor practice of having a single build (yes, we developed on the production build; we were awesome). We hadn't got the integrated testing phase before I left.

After a while, it did, however, lessen the amount of massive coding changes (compared to the "check in and pray my changes don't conflict" that was rampant). Eventually, most developers started making small changes frequently just to get confirmation from the CC.Net tray icon.

Overall, I found it very comforting to know that we could send out a build immediately if we had to. Had we had just a few smoke tests integrated, I think the stress-level would have been substantially lower.

blocks|key|235523|text|只是想刷新一下。在这一点上，持续集成(CI)和持续交付(CD)之间存在着巨大的差异。虽然上面的大多数帖子都描述了CD，但我将尝试展示CI如何扩展CD的定义。拥有构建包和自动部署新版本的应用程序所需的所有工具是CD的关键部分。除了测试自动化(基于三个级别的验证:一般健康检查、详细统计和历史条目)和适当的治理，您正在创建一个真正良好的CI。正是因为有了这样的扩展定义，才有可能构建非凡的云工具。想想muleESB或esbeetle.com。尽管只有第二个组件同时支持ESB和ETL组件，但对于这两个组件，CI是很自然的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|235524|我希望它能对你有所帮助。|235525|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Just to refresh. At this point there is a huge difference between Continuous Integration (CI) and Continuous Delivery (CD). While most of posts above described CD I'll try to show how CI extends now CD definition. Having all the tools needed to build a package and deploy new version of app automatically is a crucial part of CD. Adding to that test automation (based on three level verification: General Health-check, Detailed Statistics and Historical entries) and a proper governance you're creating a really good piece of CI. Only because of such an extended definition building extraordinary cloud tools is possible. Think about muleESB or esbeetle.com. For both of them CI is something natural although only the second one is supporting both ESB and ETL components.

I hope that it was helpful.

What is continuous integration and what are its benefits?

What is continuous integration?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

什么是持续集成?它的好处是什么？

问什么是持续集成？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是持续集成？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是持续集成？
EN