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

There are still quite a few other features related to the pull requests that we haven't explored. Specifically, we haven't looked at **GitChat**-related functionalities. The reason for that is technical. The type of Jenkins X installation we performed does not allow **GitChat**. We'll fix that later on. For now, you should have a solid base to deal with your pull request.

We're done with yet another chapter, and you are once again forced to decide whether to continue using the cluster or to destroy it. 
# How to free up the resources?
If the destruction is what you crave, you'll find the instructions at the bottom of the Gist you chose at the beginning of this chapter.

If you destroyed the cluster or you uninstalled Jenkins X, please remove the repositories and the local files we created. You can use the commands that follow for that.

> ⚠️ Please replace `[...]` with your GitHub user before executing the commands that follows.



This lesson concludes the discussion regarding this chapter and gives instructions to free up the used resources. 

What Now?