Skip to content

Add git provenance to bundle deploy telemetry - #6842

Draft
atreyadbrx wants to merge 1 commit into
mainfrom
telemetry-bundle-deploy-git
Draft

atreyadbrx wants to merge 1 commit into
mainfrom
telemetry-bundle-deploy-git

Conversation

@atreyadbrx

@atreyadbrx atreyadbrx commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

Changes

Adds git provenance to the bundle deploy telemetry event (BundleDeployEvent):

  • git (BundleGitInfo): origin_url, branch and commit, taken from b.Config.Bundle.Git. The load_git_details mutator has already resolved these and stripped credentials from the origin URL.
  • from_workspace_folder: true when the CLI runs on DBR with the bundle source under /Workspace/. This is the same check the source-linked deployment preset uses.

Why

The deploy telemetry doesn't record which git source a deployment came from. The CLI already resolves this on every deploy and writes it to metadata.json, and sends it to DMS for experimental.deployment_history bundles. None of it reaches Lumberjack, so deploys can't be tied to repos or commits at scale.

The matching universe proto change has merged: databricks-eng/universe#2674496. This PR should merge only after the Lumberjack schema pipeline has deployed those columns. Until then the new fields are dropped server-side.

Tests

acceptance/bundle/telemetry/deploy-git deploys inside a git-repo-init repo with an origin remote. It asserts the git block and from_workspace_folder in the recorded /telemetry-ext request, following the existing per-field telemetry tests (deploy-target-count, deploy-mode).


This pull request and its description were written by Isaac.

@github-actions github-actions Bot added the DABs DABs related issues label Sep 24, 2026
@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Sep 24, 2026 •

Copy link
Copy Markdown
Collaborator

Integration test report

Commit: 0fcdce3

Run: 37846491130

Env ✅​pass 🙈​skip Time
✅​ aws linux-2core-8gb 276 17 5:27
✅​ aws-windows-latest-4core-16gb 278 15 3:18
✅​ azure linux-2core-8gb 275 17 5:15
✅​ azure-windows-latest-4core-16gb 277 15 3:29
✅​ gcp linux-2core-8gb 276 17 5:17
✅​ gcp-windows-latest-4core-16gb 278 15 3:48
Top 6 slowest tests (at least 2 minutes):
duration env testname
3:59 azure linux-2core-8gb TestAccept
3:52 gcp linux-2core-8gb TestAccept
3:49 aws linux-2core-8gb TestAccept
3:46 gcp-windows-latest-4core-16gb TestAccept
3:26 azure-windows-latest-4core-16gb TestAccept
3:16 aws-windows-latest-4core-16gb TestAccept

@atreyadbrx
atreyadbrx force-pushed the telemetry-bundle-deploy-git branch 2 times, most recently from c911d63 to cf4dc1a Compare September 25, 2026 00:33
Populate the new git and from_workspace_folder fields on
BundleDeployEvent from b.Config.Bundle.Git and the deploy environment,
so a deploy's origin, branch and commit are captured in telemetry.
Requires the matching universe proto change to the frontend log.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: atreyadbrx <atreya.misra@databricks.com>
@atreyadbrx
atreyadbrx force-pushed the telemetry-bundle-deploy-git branch from cf4dc1a to 0fcdce3 Compare October 8, 2026 21:23

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

DABs DABs related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants