From 3ab3fb7272c34fc967a15ec689d4e05a78583960 Mon Sep 17 00:00:00 2001 From: Tolleiv Nietsch Date: Fri, 22 Apr 2022 15:03:02 +0200 Subject: [PATCH] update pipeline as code --- radar/2022-03-28/pipeline-as-code.md | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 radar/2022-03-28/pipeline-as-code.md diff --git a/radar/2022-03-28/pipeline-as-code.md b/radar/2022-03-28/pipeline-as-code.md new file mode 100644 index 0000000..1b84a90 --- /dev/null +++ b/radar/2022-03-28/pipeline-as-code.md @@ -0,0 +1,11 @@ +--- +title: "Pipeline as Code" +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. + +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. + +Using [container based builds](https://www.aoe.com/techradar/methods-and-patterns/container-based-builds.html) is now also the de facto standard. Combining these two techniques enables running isolated builds in an easily reproducible environment so teams can get quick feedback on every change. \ No newline at end of file