feat: Add integration test trigger workflow#188
Merged
eric-wang-1990 merged 3 commits intomainfrom Jan 28, 2026
Merged
Conversation
This workflow triggers integration tests in databricks/databricks-driver-test when PRs are ready to merge. Features: - Label-based trigger: Add 'integration-test' label to run tests on any PR - Auto re-run on new commits if label exists - Smart merge queue handling: - Only tests if relevant files changed (csharp/src, csharp/test, ci/scripts) - Skips duplicate runs if tests already passed on PR head - Auto-approves if no relevant files changed - Uses GitHub App for cross-repo authentication Relevant paths that trigger tests in merge queue: - .github/workflows/trigger-integration-tests.yml - ci/scripts/** - csharp/src/** - csharp/test/** Requires GitHub App setup with secrets: - INTEGRATION_TEST_APP_ID - INTEGRATION_TEST_PRIVATE_KEY Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
GitHub-hosted runners are IP-blocked from accessing the internal databricks/databricks-driver-test repository. Switch all jobs to use the self-hosted peco-team-runner which has network access. Changes: - All 7 jobs now use: runs-on: [self-hosted, Linux, X64, peco-driver] - This enables access to the internal test repository - Runner: peco-team-runner (status: online)
Collaborator
Author
|
Trigger workflow with updated App ID |
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
🚀 Integration tests triggered! View workflow run |
|
🚀 Integration tests triggered! View workflow run |
|
🚀 Integration tests triggered! View workflow run |
jadewang-db
approved these changes
Jan 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a workflow to trigger integration tests in the internal
databricks/databricks-driver-testrepository when PRs are ready to merge.How It Works
PR Phase (Flexible)
integration-testlabel to trigger tests on any PRMerge Queue Phase (Efficient)
.github/workflows/trigger-integration-tests.ymlci/scripts/**csharp/src/**csharp/test/**Benefits
✅ Cost-efficient: Only runs tests when needed
✅ Flexible: Can manually test any PR via label
✅ Smart: Avoids duplicate test runs
✅ Guards merging: Blocks merge if tests fail
Setup Required
This workflow requires GitHub App setup:
Create GitHub App with permissions:
checks: write(to report status on PRs)contents: read(to dispatch events)metadata: readInstall app on both repos:
adbc-drivers/databricks(this repo)databricks/databricks-driver-test(internal test repo)Add secrets to both repos:
INTEGRATION_TEST_APP_IDINTEGRATION_TEST_PRIVATE_KEYInternal repo needs matching workflow:
databricks/databricks-driver-test/.github/workflows/adbc-integration-tests.yml(already created)Enable merge queue in branch protection rules (optional but recommended)
Testing
After setup, test by:
integration-testlabel🤖 Generated with Claude Code