X-tra, X-tra, read all about it… or better yet listen all about it in the newest episode of DevOps Radio! Host Andre Pino discusses “it” with James Strachan, member of the Jenkins community and senior architect at CloudBees. What is “it”? Jenkins X, the new project being spun up in the community and led by James. As the original creator of the Groovy language and Apache Camel, James talks about his extensive career in open source. He also reveals that Jenkins X is the most fun open source project he’s worked on. With his pedigree in open source, that’s saying a lot!
As James introduces Jenkins X, his sets the stage by noting that in the past few years everything has changed in software delivery. With the rise of containers and Kubernetes, teams package software and run software differently. They want to release faster and faster. Jenkins X is an accelerant. With Jenkins X, developers can easily automate the entire pipeline without needing to learn the intricacies and technical details of the various technologies. Developers don’t need to really know or care about what Docker is or how it works – what a Dockerfile is, what Jenkins pipelines are and how to write one, or even how to manage multiple different environments on something like Kubernetes.
Jenkins X automates continuous integration and continuous delivery for people using the cloud and Kubernetes. For those wondering how this differs from Jenkins 2, James reassures the DevOps Radio audience that Jenkins X is still the same Jenkins we know and love, just built to better work with technologies like Docker or Kubernetes. However, you don’t need to know anything about Jenkins, Docker or Kubernetes to get started. The next generation of Jenkins is here – and it’s abstracted away all of the previous complexity. James also mentions a special preview feature that allows developers to give faster feedback about Jenkins X.
So how can people learn more? Head to jenkins-x.io, to check out the available demos and blogs, learn about the features and get started. Or find the Jenkins community on all of the following communications channels (the only one not included is smoke signals) - Slack, Twitter, IRC, Jenkins issue tracker or via email.
Don’t miss new episodes of DevOps Radio by subscribing via iTunes or Spotify or downloading the episode from the CloudBees website. You can also share your thoughts on Twitter by tweeting to CloudBees: @CloudBees, and using the #DevOpsRadio hashtag.