这三个词的区别是什么?我所在的学校提供了以下定义:
持续集成基本上意味着开发人员的工作副本每天多次与共享主线同步。
持续交付被描述为持续集成的逻辑演进:始终能够将产品投入生产!
持续部署被描述为持续交付之后的逻辑下一步:只要产品通过QA,就自动将其部署到生产环境!
它们还提供了一个警告:如果您能够持续部署到测试系统,有时也会使用术语“持续部署”。
所有这些都让我感到困惑。任何更详细的解释(或附带一个例子)都是非常感谢的!
这三个词的区别是什么?我所在的学校提供了以下定义:
持续集成基本上意味着开发人员的工作副本每天多次与共享主线同步。
持续交付被描述为持续集成的逻辑演进:始终能够将产品投入生产!
持续部署被描述为持续交付之后的逻辑下一步:只要产品通过QA,就自动将其部署到生产环境!
它们还提供了一个警告:如果您能够持续部署到测试系统,有时也会使用术语“持续部署”。
所有这些都让我感到困惑。任何更详细的解释(或附带一个例子)都是非常感谢的!
当前回答
持续集成、持续交付和持续部署之间的区别
其他回答
持续集成:不断地将开发工作与主要分支合并,以便尽可能频繁地测试代码,以便及早发现问题。
持续交付:一旦代码准备好交付,就持续地向环境交付代码。这可以是分期或生产。其理念是将产品交付给用户群,用户群可以是QA或客户,以便进行审查和检查。
持续集成阶段的单元测试不能捕捉到所有的错误和业务逻辑,特别是设计问题,这就是为什么我们需要QA或测试环境。
持续部署:在代码准备好后立即部署或发布。持续部署需要持续集成和持续交付,否则在发布版中代码质量将得不到保证。
持续部署~~持续集成+持续交付
问题和答案都不符合我简单的思考方式。我是一名顾问,并与许多开发团队和DevOps人员同步了这些定义,但我很好奇它如何与整个行业相匹配:
基本上,我认为持续交付的敏捷实践就像一个连续体:
非连续(一切手工)0% ----> 100%持续交付价值(一切自动化)
实现持续交付的步骤:
零。当开发人员签入代码时,没有什么是自动的……如果他们在签入之前已经编译、运行或执行了任何测试,那么您就很幸运了。
Continuous Build: automated build on every check-in, which is the first step, but does nothing to prove functional integration of new code. Continuous Integration (CI): automated build and execution of at least unit tests to prove integration of new code with existing code, but preferably integration tests (end-to-end). Continuous Deployment (CD): automated deployment when code passes CI at least into a test environment, preferably into higher environments when quality is proven either via CI or by marking a lower environment as PASSED after manual testing. I.E., testing may be manual in some cases, but promoting to next environment is automatic. Continuous Delivery: automated publication and release of the system into production. This is CD into production plus any other configuration changes like setup for A/B testing, notification to users of new features, notifying support of new version and change notes, etc.
EDIT: I would like to point out that there's a difference between the concept of "continuous delivery" as referenced in the first principle of the Agile Manifesto (http://agilemanifesto.org/principles.html) and the practice of Continuous Delivery, as seems to be referenced by the context of the question. The principle of continuous delivery is that of striving to reduce the Inventory waste as described in Lean thinking (http://www.miconleansixsigma.com/8-wastes.html). The practice of Continuous Delivery (CD) by agile teams has emerged in the many years since the Agile Manifesto was written in 2001. This agile practice directly addresses the principle, although they are different things and apparently easily confused.
持续集成:是开发人员尽可能频繁地将对代码库的更改合并到主分支的实践。通过创建构建,然后对构建运行自动化测试来验证这些更改。如果这些测试没有通过,更改就不会合并,开发人员就会避免可能发生的集成挑战。
Continuous Delivery : is an extension of CI since it enables automation to deploy all the code changes to an environment (dev, qa, stage, prod, etc) after the changes have been merged. The artifact may be built as part of CI or as part of this process since the source of truth (your repository) is reliable given your CI process. In simple terms, this means that there is an automated release process on top of the automated testing process and that developers can deploy their changes at any time by simply clicking a button or at the completion of CI.
持续部署:比持续交付更进一步。在这里,在管道的每个阶段通过验证步骤的所有更改都将发布到生产环境中。这个过程是完全自动化的,只有一个失败的验证步骤才能阻止将更改推到生产环境中。
一个图表可以代替很多单词:
享受吧!:-)
#我已经更新了正确的图片…
持续集成、持续交付和持续部署之间的区别