The Jenkins X team and CloudBees are excited to announce some changes that we’ve been working on and are jntroducing the new Jenkins X Pipeline Engine.
Today, there are two ways that you can run your Jenkins pipelines in Jenkins X. By default today, Jenkins X uses a static traditional Jenkins master. This mode works well for those who may have complex existing Jenkins pipelines and want to be able to use all the Jenkins X goodness of GitOps and preview environments in Kubernetes. As of last October, you can run Jenkins pipelines without the static Jenkins server – so, it’s serverless.
Serverless pipeline execution mode will become the best way to run Jenkins X in the not-too-distant future. And as we’re looking forward, we’ve begun to find ways to further improve the serverless mode of Jenkins X. Tekton is a new Kubernetes-native way of running serverless pipelines. While it’s still in its early stages, Tekton will eventually become the best way to run CI/CD pipelines in Kubernetes.
We’ve begun some early work to add Tekton into Jenkins X. You can now begin testing the pipeline, and we’d love to get your feedback. To use the new Tekton execution mode, you will include a jenkins-x.yml file with your application instead of a Jenkinsfile in your source code repository. This YAML file is organized similarly to the Jenkins declarative pipeline syntax used in a Jenkinsfile.
We’ll continue to update the community on progress accordingly and welcome your feedback! Feel free to contact the Jenkins X team via Slack, office hours or send us an email with any questions or concerns. The next office hours will be on Thursday, February 21st, at 11:00am ET and Andrew Bayer will be demoing progress. Thanks!