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

All binaries must be stored in registries.

Communication between processes must be parallel.

Everything must be tracked, actions should be reproducible, and idempotent.

Processes should run for as long as possible, but not longer.

Which GitOps principle is contradicted by using the `jx create cluster` and `jx install` commands directly?


Which GitOps principle is contradicted by using the <code>jx create cluster</code> and <code>jx install</code> commands directly?

Installing and maintaining Jenkins X and other system-level components.

Which of the following tasks does Jenkins X Boot NOT perform?

Which of the following tasks does Jenkins X Boot NOT perform?

The file that contains almost all the parameters that can be used to customize the setup is `jx-requirements.yml`.


The file that contains almost all the parameters that can be used to customize the setup is <code>jx-requirements.yml</code>.

The questions answered during execution of `jx boot` help populate the `jx-requirements.yml` file.


The questions answered during execution of <code>jx boot</code> help populate the <code>jx-requirements.yml</code> file.

They are not created in advance, but rather when used for the first time.

After running `jx boot`, if you check Namespaces using `kubectl get namespaces`, you do not see any Namespaces for staging and production environments. Why is this?

After running <code>jx boot</code>, if you check Namespaces using <code>kubectl get namespaces</code>, you do not see any Namespaces for staging and production environments. Why is this?

---
In the next chapter, we will learn about the methods of managing third-party applications in Jenkins X.

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

Quiz