---
title: Set up continuous integration and developer workflow
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

Xperience by Kentico's _Continuous integration_ feature allows you to manage database objects through source control using the _[.NET Command Line Interface](https://learn.microsoft.com/en-us/dotnet/core/tools/)_.

While the process is described in [the documentation](https://docs.kentico.com/documentation/developers-and-admins/ci-cd/continuous-integration.md), seeing a walkthrough is often helpful.

In this video, Sean Wright walks through the process of propagating data and schema changes from one developer instance of Xperience to another using continuous integration.

> **Info:** The following video shows Xperience by Kentico release v26. CI/CD has been updated to include new Xperience features. Find out more information in the product [Changelog](https://docs.kentico.com/changelog.md). You can read about [different CI/CD development scenarios](https://community.kentico.com/blog/xperience-by-kentico-ci-cd-developer-scenarios) on the [Community portal](https://community.kentico.com/).

🎬 [Video](https://www.youtube.com/embed/5QCy7239-rA?si=o4WK8Tt2gp8rwNJg)