topic Multiple feature branches per user using Databricks Asset Bundles in Administration & Architecture

Multiple feature branches per user using Databricks Asset Bundles

cmathieu — Thu, 16 Jan 2025 23:11:23 GMT

I'm currently helping a team migrating to DABs from dbx and they would like to be able to work on multiple features at the same time.

What I was able to do is pass the current branch as a variable in the root_path and various names, so when the bundle is deployed it deploys separately from other previously deployed bundles.

This works as expected, from the same project, go to feature_branch_a and deploy in dev to Workspace/User/feature_branch_a and then go to feature_branch_b and deploy in dev also to Workspace/User/feature_branch_b. Now you have 2 bundles with their respective python wheel.

The issue that arises is with ressources. The same jobs from both versions of the packages gets overwritten for the same user. The docs does mention that what makes any bundle unique is the user/bundle name/target. While these are all different, I'm still having issues with ressources getting overwritten.

Has anyone faced the same issue?

Re: Multiple feature branches per user using Databricks Asset Bundles

cmathieu — Fri, 17 Jan 2025 03:17:16 GMT

deleting the DABs in Databricks and also in my local version under .databricks solved this one for me.

Re: Multiple feature branches per user using Databricks Asset Bundles

cmilligan262 — Wed, 21 May 2025 21:06:51 GMT

@cmathieu can you provide an example inserting the branch name? I'm trying to do the same thing

Re: Multiple feature branches per user using Databricks Asset Bundles

cmathieu — Wed, 21 May 2025 21:49:25 GMT

Yes, two ways:

- you can refer to the branch name directly using ${bundle.git.branch}

- create your own variable, then define that variable in your deployment script

We go with the second option in order to be able to clean up the name, like replacing / with _.