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

Should you be upgrading your cluster with every new release?

Should you be upgrading your cluster with every new release?

It makes it easier for us to fix the issues. 

How does applying smaller changes more frequently gives us more control? (Multiple correct options)

How does applying smaller changes more frequently gives us more control? (Multiple correct options)

Run a test instance in parallel with production (e.g., in separate Namespaces).

What are the prefered strategies for upgrading Jenkins X? (Multiple correct ooptions)


What are the prefered strategies for upgrading Jenkins X? (Multiple correct ooptions)

Backing up your cluster will help in the worst-case scenario and you will be able to restore the last known working state.

Backing up your cluster will help in the worst-case scenario and you will be able to restore the last known working state.

We can change the domain of the cluster or a namespace.

We can add TLS certificates to all Ingress endpoints.

We can change the template Jenkins X is using to auto-generate addresses of applications.

Which of the following task can be done using `jx upgrade ingress`?


Which of the following task can be done using <code>jx upgrade ingress</code>?

`backup-service-staging-play-with-jx.com`

`backup-service.staging.play-with-jx.com`

`backup-service.play-with-jx.staging.com`

`backup-service.staging-play-with-jx.com`

Using the default configuration, if we have a service called `backup-service` in a cluster accessible through the domain `play-with-jx.com` and deployed to the  Namespace `staging`, then the application would be accessible through the address:


Using the default configuration, if we have a service called <code>backup-service</code> in a cluster accessible through the domain <code>play-with-jx.com</code> and deployed to the Namespace <code>staging</code>, then the application would be accessible through the address:


---
In the next chapter, we will take a look at how to extend Jenkins X pipelines. Stay tuned!

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

Quiz