AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: fix some more spelling issues (#167)

Browse Source
This commit is contained in:
Stefan Rotsch
2023-02-22 19:40:39 +01:00
committed by Bastian
parent dd2e4e71c0
commit 94f368249e
10 changed files with 65 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
radar/2022-03-28/pipeline-as-code.md
View File

@@ -2,11 +2,17 @@
title: "Pipeline as Code"
ring: adopt
quadrant: methods-and-patterns
tags: [devops]
tags: [devops]
---
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.
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.
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.
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.