---
title: How does Databricks support CI/CD for machine learning? | Databricks on AWS
source: https://docs.databricks.com/aws/en/machine-learning/mlops/ci-cd-for-ml
ingestedAt: "2026-06-18T08:11:31.224Z"
---

CI/CD (continuous integration and continuous delivery) refers to an automated process for developing, deploying, monitoring, and maintaining your applications. By automating the building, testing, and deployment of code, development teams can deliver releases more frequently and reliably than manual processes still prevalent across many data engineering and data science teams. CI/CD for machine learning brings together techniques of MLOps, DataOps, ModelOps, and DevOps.

This article describes how Databricks supports CI/CD for machine learning solutions. In machine learning applications, CI/CD is important not only for code assets, but is also applied to data pipelines, including both input data and the results generated by the model.

![End-to-end MLOps lifecycle diagram showing elements of CI/CD for ML.](https://docs.databricks.com/aws/en/assets/images/end-to-end-ml-cycle-9fb31742b1e4b214fad6286566a6e642.png)

## Machine learning elements that need CI/CD[​](#machine-learning-elements-that-need-cicd "Direct link to Machine learning elements that need CI/CD")

One of the challenges of ML development is that different teams own different parts of the process. Teams may rely on different tools and have different release schedules. Databricks provides a single, unified data and ML platform with integrated tools to improve teams' efficiency and ensure consistency and repeatability of data and ML pipelines.

In general for machine learning tasks, the following should be tracked in an automated CI/CD workflow:

*   Training data, including data quality, schema changes, and distribution changes.
*   Input data pipelines.
*   Code for training, validating, and serving the model.
*   Model predictions and performance.

## Integrate Databricks into your CI/CD processes[​](#integrate-databricks-into-your-cicd-processes "Direct link to Integrate Databricks into your CI/CD processes")

[MLOps](https://docs.databricks.com/aws/en/machine-learning/mlops/mlops-workflow), DataOps, ModelOps, and DevOps refer to the integration of development processes with “operations” - making the processes and infrastructure predictable and reliable. This set of articles describes how to integrate operations (“ops”) principles into your ML workflows on the Databricks platform.

Databricks incorporates all of the components required for the ML lifecycle including tools to build “configuration as code” to ensure reproducibility and “infrastructure as code” to automate the provisioning of cloud services. It also includes logging and alerting services to help you detect and troubleshoot problems when they occur.

## DataOps: Reliable and secure data[​](#dataops-reliable-and-secure-data "Direct link to DataOps: Reliable and secure data")

Good ML models depend on reliable data pipelines and infrastructure. With the Databricks Data Intelligence Platform, the entire data pipeline from ingesting data to the outputs from the served model is on a single platform and uses the same toolset, which facilitates productivity, reproducibility, sharing, and troubleshooting.

![DataOps diagram](https://docs.databricks.com/aws/en/assets/images/ci-cd-dataops-644c74cbfc7bb5f085b148bc574ca76b.png)

### DataOps tasks and tools in Databricks[​](#dataops-tasks-and-tools-in-databricks "Direct link to DataOps tasks and tools in Databricks")

The table lists common DataOps tasks and tools in Databricks:

## ModelOps: Model development and lifecycle[​](#modelops-model-development-and-lifecycle "Direct link to ModelOps: Model development and lifecycle")

Developing a model requires a series of experiments and a way to track and compare the conditions and results of those experiments. The Databricks Data Intelligence Platform includes MLflow for model development tracking and the MLflow Model Registry to manage the model lifecycle including staging, serving, and storing model artifacts.

After a model is released to production, many things can change that might affect its performance. In addition to monitoring the model's prediction performance, you should also monitor input data for changes in quality or statistical characteristics that might require retraining the model.

![ModelOps diagram](https://docs.databricks.com/aws/en/assets/images/ci-cd-modelops-7598ac2dfe894de46984b67516e961c7.png)

### ModelOps tasks and tools in Databricks[​](#modelops-tasks-and-tools-in-databricks "Direct link to ModelOps tasks and tools in Databricks")

The table lists common ModelOps tasks and tools provided by Databricks:

## DevOps: Production and automation[​](#devops-production-and-automation "Direct link to DevOps: Production and automation")

The Databricks platform supports ML models in production with the following:

*   End-to-end data and model lineage: From models in production back to the raw data source, on the same platform.
*   Production-level Model Serving: Automatically scales up or down based on your business needs.
*   Jobs: Automates jobs and create scheduled machine learning workflows.
*   Git folders: Code versioning and sharing from the workspace, also helps teams follow software engineering best practices.
*   [Declarative Automation Bundles](https://docs.databricks.com/aws/en/dev-tools/bundles/): Automates the creation and deployment of Databricks resources, such as jobs, registered models, and serving endpoints.
*   [Databricks Terraform provider](https://docs.databricks.com/aws/en/dev-tools/terraform/): Automates deployment infrastructure across clouds for ML inference jobs, serving endpoints, and featurization jobs.

### Model serving[​](#model-serving "Direct link to Model serving")

For deploying models to production, MLflow significantly simplifies the process, providing single-click deployment as a batch job for large amounts of data or as a REST endpoint on an autoscaling cluster. The integration of Databricks Feature Store with MLflow also ensures consistency of features for training and serving; also, MLflow models can automatically look up features from the Feature Store, even for low latency online serving.

The Databricks platform supports many model deployment options:

*   Code and containers.
*   Batch serving.
*   Low-latency online serving.
*   On-device or edge serving.
*   Multi-cloud, for example, training the model on one cloud and deploying it with another.

For more information, see [Model Serving](https://docs.databricks.com/aws/en/machine-learning/model-serving/).

### Jobs[​](#jobs "Direct link to Jobs")

[Lakeflow Jobs](https://docs.databricks.com/aws/en/jobs/) allow you to automate and schedule any type of workload, from ETL to ML. Databricks also supports integrations with popular third party [orchestrators like Airflow](https://docs.databricks.com/aws/en/jobs/how-to/use-airflow-with-jobs).

### Git folders[​](#git-folders "Direct link to Git folders")

The Databricks platform includes Git support in the workspace to help teams follow software engineering best practices by performing Git operations through the UI. Administrators and DevOps engineers can use APIs to set up automation with their favorite CI/CD tools. Databricks supports any type of Git deployment including private networks.

For more information about best practices for code development using Databricks Git folders, see [CI/CD workflows with Git integration and Databricks Git folders](https://docs.databricks.com/aws/en/repos/ci-cd) and [Use CI/CD](https://docs.databricks.com/aws/en/dev-tools/ci-cd/). These techniques, together with the Databricks REST API, let you build automated deployment processes with GitHub Actions, Azure DevOps pipelines, or Jenkins jobs.

### Unity Catalog for governance and security[​](#unity-catalog-for-governance-and-security "Direct link to Unity Catalog for governance and security")

The Databricks platform includes [Unity Catalog](https://docs.databricks.com/aws/en/data-governance/unity-catalog/), which lets admins set up fine-grained access control, security policies, and governance for all data and AI assets across Databricks.
