Pipelines As Code

Define your pipelines as code with your applications and environments

Define your Continuous Integration and Continuous Delivery Pipelines as code and keep them in git with your application code.

In Jenkins X you can see the Source Layout for more detail using standard Tekton Pipelines YAML for defining pipelines in a cloud native self-contained way.

One downside with Pipelines As Code is that you can end up copy/pasting lots of YAML into lots of repositories which can become tricky to both maintain and to keep on recent images and configurations.

For details of the approach we use on Jenkins X check out this blog post on GitOps your cloud native pipelines which lets us share versioned pipelines via git while also making it super easy to override pipeline steps as and when required keeping things super flexible while maximising reuse and making it easy to maintain and upgrade.


Last modified March 29, 2021: fix: first spike of a CD pattern catalog (b315f03891)