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

Using the `\` symbol and indenting all the lines with the commands.

Using the `|` symbol to separate all the lines of the command.

Using the `|` symbol and indenting all the lines with the commands.

How do we add multiline commands in `jenkins-x.yml `?

How do we add multiline commands in <code>jenkins-x.yml </code>?

It should not contain any “special” characters.

It should contain only lower-case letters.

The words should be separated with dashes (`-`).

It is preferred that the names of steps in `jenkins-x.yml` follow the rule:

It is preferred that the names of steps in <code>jenkins-x.yml</code> follow the rule:

This step executes the given shell command.

This step specifies where the entire pipeline, or a specific stage, will execute.

This step defines a list of stages to run sequentially in each cell.

What is the purpose of the `agent` step ?

What is the purpose of the <code>agent</code> step ?

```yaml
...
    overrides:
    - pipeline: release
      stage: build
...
```

```yaml
...
    overrides:
    - pipeline: release
      - stage: build
...
```

```yaml
...
    overrides:
    - release: build
...
```

```yaml
...
    overrides:
     pipeline: build
       stage: release
...
```

If we want to override the `build` step of the `release` pipeline, the syntax would be:

If we want to override the <code>build</code> step of the <code>release</code> pipeline, the syntax would be:

Loops can contain the following: (Multiple correct options)

Loops can contain the following: (Multiple correct options)

The `jx step syntax schema` command is used to consult the full syntax schema of `jenkins-x.yml` or for build packs’ `pipeline.yaml` files.

The <code>jx step syntax schema</code> command is used to consult the full syntax schema of <code>jenkins-x.yml</code> or for build packs’ <code>pipeline.yaml</code> files.

---
In the next chapter, we will discuss how to define and run serverless deployments. 

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

Quiz