Learn how to use Jenkins X to automate your pipeline and achieve CI/CD.

DevOps for Developers

Jenkins X is a powerful tool for providing software developers continuous integration, automated testing, and continuous delivery, known as CI/CD, in Kubernetes.

It’s no secret that Kubernetes is extremely complex, and Jenkins X helps you by simplifying processes into concepts that can be adopted quickly and without spending months trying to figure out “the right way to do stuff.”

In this course, you’ll start by exploring the inner workings of Jenkins X and how to create a cluster using it. You’ll then learn how to combine Jenkins X with tools you’re already using. Throughout, you’ll see how this exciting new tool changes how you work with Kubernetes.

By the time you’re done, you will be confident managing CI/CD using Jenkins X in a Kubernetes cluster.

Jenkins X with Kubernetes

What is the default deployment strategy used by Jenkins X?

What is the default deployment strategy used by Jenkins X?

If you are not part of a self-sufficient team, should you be concerned about the deployment method?

If you are not part of a self-sufficient team, should you be concerned about the deployment method?

Deployment is a process through which we would install new applications into our servers or update those that are already running with new releases.

Deployment is a process through which we would install new applications into our servers or update those that are already running with new releases.

Serverless deployments completely fulfill the responsiveness requirement.

Serverless deployments completely fulfill the responsiveness requirement.

Rollback feature does not exist with the `RollingUpdate` strategy. 

Rollback feature does not exist with the <code>RollingUpdate</code> strategy.

Blue-green strategy is better than the `RollingUpdate` or serverless strategy. 

Blue-green strategy is better than the <code>RollingUpdate</code> or serverless strategy.

Canary deployments are, in a way, an extension of rolling updates. As such, all of the requirements fulfilled by one are fulfilled by the other.

Canary deployments are, in a way, an extension of rolling updates. As such, all of the requirements fulfilled by one are fulfilled by the other.

---
In the next chapter, we will be applying the GitOps principles to Jenkins X. 

Let's solve a quiz and review some of the material we covered in this chapter. 

Quiz