# Rasa CI/CD Pipeline Documentation

You are viewing documentation for a legacy Rasa product. If you want to get started building assistants with Rasa please check out our latest [documentation here](/content/docs/index.html).

When improving your assistant, you’ll make different kinds of [fixes](https://legacy-docs-enterprise.rasa.com/docs/rasa-enterprise/user-guide/fix-problems) to your bot. To automate the testing and integration of these improvements into your deployed assistant, you should set up a CI/CD (Continuous Integration/Continuous Deployment) pipeline on your connected git repository.

For example, you could add a step in your pipeline that pushes a newly trained model to Rasa Enterprise every time a change is merged into your main branch. For more information on setting up a CI/CD pipeline, check out the Rasa Open Source [user guide on CI/CD](/content/docs/rasa/setting-up-ci-cd/index.html).

Here are a few examples of CI/CD pipelines in [Github Actions](https://github.com/features/actions) to get you started:

- The [rasa-demo](https://github.com/RasaHQ/rasa-demo/tree/master/.github/workflows) CI/CD pipeline includes the following steps; some are conditional:
  - Lints and type-tests the action code
  - Validates the data
  - Runs NLU cross-validation
  - Trains a model
  - Tests the model on [test conversations](/content/docs/rasa/user-guide/testing-your-assistant/#end-to-end-testing/index.html)
  - Builds and tags an action image
  - Pushes the action image to a private Google Cloud Container Registry
- This example includes some of the steps above, but with fewer conditions:
  - [carbon-bot](https://github.com/RasaHQ/carbon-bot/blob/master/.github/workflows/model_ci.yml)
- This example includes the steps above, but also includes steps to create an AWS EKS cluster and deploy the bot there:
  - [financial-demo](https://github.com/RasaHQ/financial-demo/blob/c7d0f6f5f0c5859dda059db0936473131cd785b5/.github/workflows/cicd.yml#L156-L240)