# Setting up CI/CD

Even though developing a contextual assistant is different from developing traditional software, you should still follow software development best practices. Setting up a Continuous Integration (CI) and Continuous Deployment (CD) pipeline ensures that incremental updates to your bot are improving it, not harming it.

## Overview

Continuous Integration (CI) is the practice of merging in code changes frequently and automatically testing changes as they are committed. Continuous Deployment (CD) means automatically deploying integrated changes to a staging or production environment. Together, they allow you to make more frequent improvements to your assistant and efficiently test and deploy those changes.

This guide will cover **what** should go in a CI/CD pipeline, specific to a Rasa project. **How** you implement that pipeline is up to you. There are many CI/CD tools out there, such as [GitHub Actions](https://github.com/features/actions), [GitLab CI/CD](https://docs.gitlab.com/ee/ci/), [Jenkins](https://jenkins.io/doc/), and [CircleCI](https://circleci.com/docs/2.0/). We recommend choosing a tool that integrates with whatever Git repository you use.

## Continuous Integration (CI)

The best way to improve an assistant is with frequent [incremental updates](/content/docs/rasa-x/user-guide/fix-problems/index.html). No matter how small a change is, you want to be sure that it doesn’t introduce new problems or negatively impact the performance of your assistant.

It is usually best to run CI checks on merge/pull requests or on commit. Most tests are quick enough to run on every change. However, you can choose to run more resource-intensive tests only when certain files have been changed or when some other indicator is present. For example, if your code is hosted on Github, you can make a test run only if the pull request has a certain label (e.g. “NLU testing required”).

### Validate Data and Stories

[Data validation](https://legacy-docs-v1.rasa.com/1.10.21/user-guide/validate-files/#validate-files) verifies that there are no mistakes or major inconsistencies in your domain file, NLU data, or story data.

```bash
rasa data validate --fail-on-warnings --max-history <max_history>
```

If data validation results in errors, training a model will also fail. By including the `--fail-on-warnings` flag, validation will also fail on warnings about problems that won’t prevent training a model, but might indicate messy data, such as actions listed in the domain that aren’t used in any stories.

### Train a Model

```bash
rasa train
```

Training a model verifies that your NLU pipeline and policy configurations are valid and trainable, and it provides a model to use for test conversations. If it passes the CI tests, then you can also [upload the trained model](https://legacy-docs-v1.rasa.com/1.10.21/user-guide/setting-up-ci-cd/#uploading-a-model) to your server as part of the continuous deployment process.

### Test the Assistant

Testing your trained model on [test conversations](https://legacy-docs-v1.rasa.com/1.10.21/user-guide/testing-your-assistant/#end-to-end-testing) is the best way to have confidence in how your assistant will act in certain situations. These stories, written in a modified story format, allow you to provide entire conversations and test that, given this user input, your model will behave in the expected manner.

```bash
rasa test --stories tests/conversation_tests.md --fail-on-prediction-errors
```

The `--fail-on-prediction-errors` flag ensures the test will fail if any test conversation fails.

### Compare NLU Performance

If you’ve made significant changes to your NLU training data (e.g. splitting an intent into two intents or adding a lot of training examples), you should run a [full NLU evaluation](https://legacy-docs-v1.rasa.com/1.10.21/user-guide/testing-your-assistant/#nlu-evaluation). You’ll want to compare the performance of the NLU model without your changes to an NLU model with your changes.

You can do this by running NLU testing in cross-validation mode:

```bash
rasa test nlu --cross-validation
```

### Test Action Code

The approach used to test your action code will depend on how it is implemented. For example, if you connect to external APIs, it is recommended to write unit tests to ensure that those APIs respond as expected to common inputs. However you test your action code, you should include these tests in your CI pipeline so that they run each time you make changes.

## Continuous Deployment (CD)

To get improvements out to your users frequently, you will want to automate as much of the deployment process as possible.

CD steps usually run on push or merge to a certain branch, once CI checks have succeeded.

### Deploy your Rasa Model

If you ran [end-to-end tests](https://legacy-docs-v1.rasa.com/1.10.21/user-guide/setting-up-ci-cd/#test-the-assistant) in your CI pipeline, you’ll already have a trained model. You can set up your CD pipeline to upload the trained model to your Rasa server if the CI results are satisfactory.

```bash
curl -k -F "model=@models/my_model.tar.gz" "https://example.rasa.com/api/projects/default/models?api_token={your_api_token}"
```

### Deploy your Action Server

You can automate [building and uploading a new image for your action server](https://legacy-docs-v1.rasa.com/1.10.21/user-guide/how-to-deploy/#building-an-action-server-image), to an image repository for each update to your action code.

## Example CI/CD pipelines

As examples, see the CI/CD pipelines for [Sara](https://github.com/RasaHQ/rasa-demo/blob/master/.github/workflows/build_and_deploy.yml), the Rasa assistant that you can talk to in the Rasa Docs, and [Carbon Bot](https://github.com/RasaHQ/carbon-assistant/blob/master/.github/workflows/model_ci.yml). Both use [Github Actions](https://github.com/features/actions) as a CI/CD tool.

These examples are just two of many possibilities. If you have a CI/CD setup you like, please share it with the Rasa community on the [forum](https://forum.rasa.com/).