Understand this story
On November 1, 2026, Databricks published a post describing how Snorkel AI uses Lakebase branches to create an independent, read-write database for each open PR in its CI/CD practice. According to the Databricks blog, this approach reduces branch readiness time from over 30 minutes to under 60 seconds; branches use copy-on-write, and on a production dataset of about 2.5 TB, 100 concurrent PR branches store only an additional 5 to 10 GB of data for their respective changes, with automatic cleanup via TTL after the PR ends. Production data is continuously synchronized to the main branch via AWS DMS, developers log in with Okta SSO, and the CI pipeline authenticates with a service principal and short-lived OAuth tokens. There are currently no further developments.
AI-generated from public reports
Latest development · Report
Databricks uses Lakebase branching to create an independent database per PR: a CI/CD practiceDevelopments
1 confirmed developments
Databricks highlights how Snorkel AI uses Lakebase branching to support CI/CD
Source:Databricks Blog
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Nov 1
Databricks BlogFirst-party
Databricks uses Lakebase branching to create an independent database per PR: a CI/CD practice
Databricks describes Snorkel AI's CI/CD solution that uses Lakebase branching to create an independent read-write database for each open PR, reducing branch readiness time from over 30 minutes to under 60 seconds. Branches use copy-on-write; on a production dataset of about 2.5 TB, 100 concurrent PR branches store only 5 to 10 GB of data each for their own changes, and TTL automatically cleans them up after the PR ends. Production data is continuously synchronized to the main branch via AWS DMS; developers log in with Okta SSO, and the CI pipeline authenticates with a service principal and short-lived OAuth tokens.