- Continuous Integration,Delivery,and Deployment
- Sander Rossel
- 455字
- 2021-07-02 15:42:11
Continuous Deployment
The final stage of automating your software development process is Continuous Deployment. When practicing Continuous Deployment, every check into your source control is deployed to a production (like) environment on a successful build. The rationale behind this is that you are going to deploy the software to production sooner or later anyway. The sooner you do this, the better the chance you'll be able to fix bugs faster. It's easier to remember what you did yesterday that might have caused the bug than it is to remember what you did two months ago that might have caused the bug. Imagine checking some code into source control and get error messages from your production environment five minutes later. You'll be able to find and fix the bug immediately and, five minutes later, the production software is up and running without bugs again. Unfortunately, most managers and software owners I know get pretty nervous at the thought of automated deployment, let alone automated deployment on every check in.
Again, as with Continuous Delivery, Continuous Deployment is not always possible. All the issues with Continuous Delivery still apply, except now when a DBA doesn't give you access to the database, Continuous Deployment is pretty much out of the question. After all, you can't automatically deploy software multiple times a day while your database is only updated when some DBA has time. Currently, I'm working on a website for a customer who in turn has a customer who needs three days' notice before any changes to the website can be made. It's a contractual obligation and whether it makes sense or not, it is what it is. So in that particular case, Continuous Deployment is obviously a no-go. Still, we use this technique on our own test environment and automate as much as possible while still giving three days, notice.
The difference between Continuous Integration, Continuous Delivery, and Continuous Deployment may still be a bit vague. Consider the following image (I apologize for my poor MS Paint skills) which indicates where the three types start and stop:

- Building Modern Web Applications Using Angular
- Learning Docker
- 零基礎學Python數(shù)據(jù)分析(升級版)
- Learning Python by Building Games
- Mastering Android Development with Kotlin
- Java網(wǎng)絡編程核心技術(shù)詳解(視頻微課版)
- C專家編程
- Hands-On Kubernetes on Windows
- Instant Apache Camel Messaging System
- Three.js權(quán)威指南:在網(wǎng)頁上創(chuàng)建3D圖形和動畫的方法與實踐(原書第4版)
- Python Automation Cookbook
- ASP.NET Core and Angular 2
- HTML5 WebSocket權(quán)威指南
- C/C++代碼調(diào)試的藝術(shù)
- Spring Web Services 2 Cookbook