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

fade out items and adjust description of updated items

Browse Source
This commit is contained in:
Daniel Pötzinger
2018-05-09 11:46:06 +02:00
parent ab121fae6d
commit eb27cbfdef
23 changed files with 52 additions and 78 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
radar/2017-10-01/pipeline-as-code.md
View File

@@ -5,8 +5,6 @@ quadrant: methods-and-patterns
---
Continuous Integration and Delivery is a critical part of our development and deployment process at AOE. Using Jenkins for many years the "instructions" how to build, test and deploy applications were scattered between many custom scripts and the pipeline was often maintained by manual maintenance of Jenkins jobs. Soon, we realized that we need a more native way to express the full CI/CD pipeline process in code and manage it in version control.
We moved this pattern to adopt, because it is used by nearly every team and project now and is an important part of our automation.
Being an important part of each project, the pipeline configuration should be managed as code and rolled out automatically - this also allows us to manage the pipeline itself applying the same standards that apply to application code.
While some teams started using Jenkins' [JobDSL plugin,](https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin) others explored the new [Jenkins Pipeline](https://jenkins.io/doc/book/pipeline/) - in both ways, the build artifacts should be published to an artifact repository such as [Artifactory.](/platforms-and-aoe-services/artifactory.html)
For Jenkins we often use a mix of Job DSL and Jenkins Pipelines and recently also Gitlab Pipelines.