The road to streamlining CI/CD through DevOps in the shift to cloud native is hard — and can be fraught with peril. That, of course, is the challenge — while the potential rewards are significant, indeed.
Automating all of that (an essential part of DevOps) set the stage for Jenkins to help streamline CI/CD processes, which represents another subset challenge. While remaining essential for many organizations’ development processes, Jenkins is notoriously difficult to master and manage, especially as projects are scaled. (This actually spells opportunities for those who can serve as in-house Jenkins experts of sorts, but such a specialty, in many ways, goes against the spirit of DevOps.)
Now, as we enter the world of Cloud Native, extending Jenkins to new platforms, as well as CI/CD processes that may have worked reasonably well for monolithic deployments in the past, adds yet another technical challenge. Thus enters the utility of Jenkins X, which serves as tool to help standardize how to integrate CI and CD and Kubernetes. The idea is also to allow organizations to use their own source code while CloudBees’ Jenkins X automates the process as it is ported to cloud native environments.
As part of “The New Stack Guide to Cloud Native DevOps” ebook podcast series, some of CloudBees’ key team members were on hand to discuss how Jenkins X, CI/CD and DevOps all elegantly fit together in today’s cloud native world.