CICD Folder structure for team of 10 Members

[naveenbandla]

Hi Everyone,

We are in the process of setting up a CI/CD framework for our Databricks ecosystem, and I have a general question around best practices.

We are a team of 10 members, and I’m trying to understand the ideal way to structure our repository and Databricks assets. I’ve gone through several blog posts, but I’m seeing mixed approaches.

Specifically:

• Should we maintain a single top-level databricks.yml and deploy everything for every change?

• Or is it better to organize assets project-wise (or domain-wise), each with its own configuration, so changes are scoped only to the relevant project?

I’d like to understand what is generally followed across companies and what has worked well in practice for scalability, collaboration, and controlled deployments.

Looking forward to your inputs and recommendations.

Thanks!

[dbxdev]

If the work is owned by the same team, you can use a single databricks.yml. Each team member develops and tests their own resource locally, then commits to Git. At deployment time, you can either deploy all resources (using a wildcard) or target only the specific resources that changed. In development mode, resource names are automatically prefixed with the deploying user’s ID, which prevents naming conflicts across teammates so its safe and simpler to use a single databricks.yml