From 181bee755e521f0d328f06cb0504641ee9af41ad Mon Sep 17 00:00:00 2001 From: Rasheed Amir Date: Sun, 3 Feb 2019 09:23:54 +0100 Subject: [PATCH] add continuous deployment vs continuous delivery --- git/tbd.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/git/tbd.md b/git/tbd.md index 2766cc2..8cc6d09 100644 --- a/git/tbd.md +++ b/git/tbd.md @@ -16,6 +16,8 @@ trunk-based development (TBD) continuous delivery (CD) workflow > The pattern that is central to Continuous Delivery is the deployment pipeline. A **deployment pipeline** is, in essence, an automated implementation of your application’s build, deploy, test, and release process. Every organization will have differences in the implementation of their deployment pipelines, depending on their value-stream for releasing software, but the principles that govern them do not vary +> Continuous deployment is the next step of continuous delivery: Every change that passes the automated tests is deployed to production automatically. + # Common anti-patterns with branch based workflows? ---