Continuous Integration and Delivery with Jenkins X and Kubernetes

5 Sep 2018 12:48pm, by

This podcast has been sponsored by CloudBees.

When the technology industry aligns behind Kubernetes, application lifecycle management may become much easier. These days, only the CI half of continuous integration and continuous delivery (CI/CD) is automated. CD is assembled by hand with scripts, pipelines, metadata and configurations. But Kubernetes enables CD automation, and tools like Jenkins X make it simple to deploy on Kubernetes.

“CI/CD should become increasingly like an appliance that just does CI and CD for you. It’s not this kind of ninja scripty thing that only experts can figure out,” said James Strachan, chief architect at CloudBees. “Where we’re trying to go with Jenkins X is not so much hiding Kubernetes, not so much hiding CI and CD and pipelines, but just automating it.”

In this podcast, Michael Neale, CloudBees co-founder and engineering manager, and Strachan discuss how Kubernetes has changed CI/CD, evolving workflows such as GitOps, and how CloudBees is working to improve the developer experience for application deployments on top of Kubernetes.

In this Edition:

2:56: What are your thoughts on CI/CD with Kubernetes?
13:51: What about the deployment, automation, testing, security, monitoring, and all of those key components that come with managing Kubernetes?
23:37: How do you perceive the contractual divide between dependencies and serverless in an application architecture?
30:06: Explaining the perspective of Jenkins X
34:24: Exploring the acquisition of Codeship by CloudBees
39:54: Are there any thoughts you have going into these last few months of the year surrounding Kubernetes, containers, and serverless?

Feature image via Pixabay.

This post is part of a larger story we're telling about the Kubernetes ecosystem.

Get the Full Story in the Ebook

Get the Full Story in the Ebook

View / Add Comments

Please stay on topic and be respectful of others. Review our Terms of Use.