Have you answered the Jenkins X survey yet?
If no, then
Pipelines As Code
Define your Continuous Integration and Continuous Delivery Pipelines as code and keep them in git with your application code.
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.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.