From 861fbe939d5e35196af1ac89a3a4ebe2ef2f22c1 Mon Sep 17 00:00:00 2001 From: Tolleiv Nietsch Date: Fri, 22 Apr 2022 15:07:42 +0200 Subject: [PATCH] adjust link to codedeploy --- radar/2022-03-28/pipeline-as-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/radar/2022-03-28/pipeline-as-code.md b/radar/2022-03-28/pipeline-as-code.md index 1b84a90..bdae7a7 100644 --- a/radar/2022-03-28/pipeline-as-code.md +++ b/radar/2022-03-28/pipeline-as-code.md @@ -4,7 +4,7 @@ ring: adopt quadrant: methods-and-patterns --- -In the past years many tools have evolved and especially [Gitlab CI](https://docs.gitlab.com/ee/ci/), [Github Actions](https://github.com/features/actions) and [AWS CodeDeploy](AWS CodeDeploy) matured or became available and widely used across many teams. +In the past years many tools have evolved and especially [Gitlab CI](https://docs.gitlab.com/ee/ci/), [Github Actions](https://github.com/features/actions) and [AWS CodeDeploy](https://aws.amazon.com/de/codedeploy/) matured or became available and widely used across many teams. Continuous Integration and Delivery is an important part in every project. Pipelines which are maintained as code, can now be handled like most other parts of your software. The pipeline configuration can run through lint checks, or a test suite before the configuration is shared across teams in your organisation.