What Now?

If you are using static Jenkins X, you should consider relying on build packs as much as possible. Serverless Jenkins X is the future, and most of the effort to create new features and fix bugs will be focused around it. On the other hand, static Jenkins X is in “maintenance mode”. But that doesn’t mean that you should use it. There are quite a few reasons why static Jenkins X might be a better option for you but we won’t cover those now. I’m mentioning all this because you will move to serverless Jenkins X at some point and you don’t want to spend your precious time rewriting your multiple Jenkinsfile into the jenkins-x.yml format. If most of your pipelines are in build packs, you can easily switch from static to serverless Jenkins X. All you’d have to do is re-import your project and let Jenkins X convert the pipeline into the correct format

🔍 We explored only a fraction of the Jenkins X pipeline syntax. Please consult Jenkins X Pipeline Syntax Reference for more info.

Before we leave, we’ll restore the master to the extension-model-cd. Our jenkins-x.yml became too big for future examples so we’ll go back to the much simpler one we had at the beginning of this chapter. I will assume that you understood the constructs we used and that you will extend that knowledge by exploring the pipeline schema. If we keep adding everything we’ve learned to our go-demo-6 pipeline, we’d need multiple pages just to list out jenkins-x.yml content.