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

GitOps is a method of Continuous Delivery that treats Git as the single source of truth, meaning infrastructure or application changes are made by pushing to Git instead of making manual changes.


GitOps is a method of Continuous Delivery that treats Git as the single source of truth, meaning infrastructure or application changes are made by pushing to Git instead of making manual changes.

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.

Which of the following are NOT GitOps commandments? Select all that apply.

Which of the following are NOT GitOps commandments? Select all that apply.

The environments where the action (building, testing, etc.) is happening.

`Permanent` environments are those where our releases should run indefinitely.

What are <code>Permanent</code> environments?

In environments where promotion is set to `Manual`, new releases are not deployed automatically through a pipeline. Instead, a specific release must be selected and deployed to production at a chosen time.


In environments where promotion is set to <code>Manual</code>, new releases are not deployed automatically through a pipeline. Instead, a specific release must be selected and deployed to production at a chosen time.

It sets promotion for each environment to `Auto`.

It outputs the environments which have promotion set to `Auto`.

What does the following command do?
```shell
jx get env --promote Auto
```

What does the following command do?
<pre><code class="language-shell">jx get env --promote Auto
</code></pre>

Their goal is to validate whether the system works as a whole.

Their goal is to check that the features of an application behave as expected.

What is the purpose of application-specific tests?

What is the purpose of application-specific tests?

Unit tests fall under the ____________ category.

Unit tests fall under the ____________ category.

The `development` environment is where all the applications are promoted automatically whenever we push a change to the master branch.

The `development` environment runs the tools we need for continuous delivery as well as temporary Pods used during builds.

What is the role of the `development` environment?

What is the role of the <code>development</code> environment?

----
The next chapter will shed light on how we can improve and simplify the process of software development using DevPods in Jenkins X and more! 


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


Quiz

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