How to Make User Interfaces, Pipelines and Jenkins X an Easier Fit

Episode 539 · November 26th, 2019 · 32 mins 50 secs

About this Episode

The idea is to empower all DevOps' stakeholders with better access to continuous integration (CI)/continuous delivery (CD) pipelines. Your organization also very likely relies on Jenkins as the backbone for the production pipeline with a reliance on Git to share and collaborate.

However, the problem has long been that Jenkins is notoriously hard to implement and use for many organizations. The added complexities of shifting to cloud native and Kubernetes platforms have further compounded the difficulties — but this new age of Jenkins and cloud native deployments have also set the stage for the creation of CloudBees' open source Jenkins X. CloudBees created Jenkins X mainly to help facilitate and automate CD pipelines to Kubernetes and cloud native environments. The idea is also to allow Jenkins X to make it easier to develop and deploy cloud native applications to Kubernetes without having to learn the intricacies of the orchestrator. Jenkins X is also one of four projects of the Continuous Delivery Foundation (CDF), which also includes Jenkins, Spinnaker and Tekton.

CloudBees says it is also continuing to try and improve Jenkins X, by simplify how developers and all DevOps stakeholders work with the tool. To that end, the company has developed its first-ever graphical interface.

In this The New Stack Makers podcast recorded during KubeCon + CloudNativeCon in San Diego last week, CloudBees' Moritz Plassnig, vice president, cloud and Peter Muir, lead architect, spoke with Alex Williams, founder and editor-in-chief of The New Stack about how CloudBees continues to try to make Jenkins X both more accessible and easier to use.

Episode Links