持续集成，持续交付，从应用程序角度持续部署 [英] Continuous Integration, Continuous Delivery, Continuous Deployment from their application perspectives

问题描述

我使用Visual Studio，TFS 2015，Visual Studio Team Services和Azure /本地或远程IIS实现连续集成。
我从下面读取stackoverflow 持续集成与持续交付与连续部署

I am using Visual Studio, TFS 2015, Visual Studio Team Services, and Azure/ Local or Remote IIS for achieving Continuous Integration. I am reading from below stackoverflow Continuous Integration vs. Continuous Delivery vs. Continuous Deployment

1. 我/我的团队检查代码到TFS存储库并配置自动构建每次我检入代码;是连续集成吗？


2. 我已经配置了构建。它运行nuget包管理器，运行测试，执行构建并将构建的程序集丢弃到指定位置。是否为连续传送？


3. 我已配置部署到Azure / IIS。我也启用了连续集成。所以每当我/我的团队检查代码，它运行构建并部署到生产/陈述服务器。是否为持续部署？


4. 当我在一次单击中执行上述所有操作时，是否称为DevOps？


5. 使用Selenium / MS Build进入这张图片？

1. Me / my team check in the code to TFS repository and configured automated build each time I check in the code; is it Continuous Integration?
2. I have configured the build. It runs nuget package manager, runs Tests, performs Build and drops the built assembly to specified location. Is it Continuous Delivery?
3. I have configured Deployment to Azure/IIS. Also I have enabled Continuous Integration. So whenever now me/my team checks in the code, it runs build and deploys to the production/stating server. Is it Continuous Deployment?
4. When I perform all of the above in one single click, is it called DevOps?
5. Where the role of Manual Testing using Selenium/MS Build comes into the picture here?

请添加输入，让我知道如果我在任何地方出错。 p>

Please add inputs, let me know if I am going wrong anywhere.

推荐答案

1. 是的。准确地说，它只是CI的一种形式。在TFS中，这是
   称为CI构建。您可以通过选择
   构建定义的 CI 触发器来实现。


2. 是。


3. 是连续部署被描述为合乎逻辑的下一步
   在连续交付之后：自动将产品部署到
   生产。
意义和是
经常混合，但是他们是两个不同的概念。 DevOps有一个
更广泛的范围，并围绕文化变化，特别是
的协作参与软件交付的各种团队
（开发人员，运营，质量保证，管理等），以及自动化软件交付过程的
。连续
交付，另一方面，是一种自动化交付的方法
方面，并集中在汇集不同的进程和
执行它们更快速和更频繁。它们具有共同的
目标，并且通常结合使用来实现它们。 DevOps
和持续交付在敏捷方法和精益中共享背景
思考：小的和快速的变化，聚焦到结束
客户。他们在内部良好沟通和协作，
从而帮助实现快速上市时间，降低风险。

1. Yes. Accurately speaking, it is only a form of CI. In TFS, this is called CI build. You can achieved this by select CI trigger of the build definition.
2. Yes. It's also a way of implementation with Continuous Delivery.
3. Yes.Continuous Deployment is described as the logical next step after continuous delivery: Automatically deploy the product into production whenever it passes QA.

4. No.Continuous delivery and DevOps are similar in their meanings and are often conflated, but they are two different concepts. DevOps has a broader scope, and centers around the cultural change, specifically the collaboration of the various teams involved in software delivery (developers, operations, quality assurance, management, etc.), as well as automating the processes in software delivery. Continuous Delivery, on the other hand, is an approach to automate the delivery aspect, and focuses on bringing together different processes and executing them more quickly and more frequently. They have common end goals and are often used in conjunction to achieve them. DevOps and Continuous Delivery share a background in agile methods and lean thinking: small and quick changes with focused value to the end customer. They are well communicated and collaborated internally, thus helping achieve quick time to market, with reduced risk.

手动测试是 - 消费和劳动密集型过程到
，确保一块软件做到了应该的，无论它是如何开发的
。团队有时太过依赖单元测试，并忽略自动化和验收测试。 CI还有一些风险和挑战。这只是其中之一。

Manual testing is a time-consuming and labor-intensive process to ensure a piece of software does what it’s supposed to, no matter how fast it was developed. Teams sometimes depend too much on the unit testing and ignore automation and acceptance testing. CI also has the some risks and challenges. This is just one of them.

这篇关于持续集成，持续交付，从应用程序角度持续部署的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！