Route integration-tests trigger through emu-access runner#769
Merged
mihaimitrea-db merged 2 commits intomainfrom Apr 20, 2026
Merged
Route integration-tests trigger through emu-access runner#769mihaimitrea-db merged 2 commits intomainfrom
mihaimitrea-db merged 2 commits intomainfrom
Conversation
Co-authored-by: Isaac
hectorcast-db
approved these changes
Apr 20, 2026
…k-trigger-tests-emu-access
Contributor
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
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
Moves the
trigger-testsjob in.github/workflows/integration-tests.ymlfrom thedatabricks-deco-testing-runner-grouptodatabricks-release-runner-group-emu-access, so the cross-org GitHub App installation lookup againstdatabricks-engcan succeed.databricks-deco-testing-runner-groupdatabricks-release-runner-group-emu-accessubuntu-latest-decolinux-ubuntu-latest-emu-accessWhy
Between 2026-04-17 and 2026-04-20, the
databricksorg tightened its IP allow list. Since then, every PR-triggered Integration Tests run on this repo has failed:create-github-app-tokenresolves the installation for${{ secrets.ORG_NAME }}(databricks-eng) by calling/repos/databricks-eng/.../installation.gh workflow run sdk-java-isolated-pr.yml -R databricks-eng/...dispatch never happens.merge_groupauto-approves the check without running tests.The
emu-accessrunner pool's egress IPs are on the allow list, so the installation lookup succeeds from there.Where the changes come from
Ported from the Go SDK fix: databricks/databricks-sdk-go#1638 (supersedes #1616, verified green end-to-end on 2026-04-10).
The Go PR splits
trigger-testsinto two jobs:create-check— stays on deco, creates a same-org check run via thedatabricks/...check-runs API.trigger-tests— moves to emu-access, performs the cross-orgworkflow_dispatch.What this PR does differently
The Java SDK's
integration-tests.ymldoes not create a check run in the PR flow —trigger-testsonly performs the cross-org dispatch. Nothing needs to stay on the deco runner, so the equivalent minimal fix is a single runner-group change on the existing job rather than a two-job split. No job splitting, added dependencies, orcheck_run_idplumbing was needed here.Matches the equivalent Python SDK fix: databricks/databricks-sdk-py#1396.
How is this tested
This PR's own Integration Tests run is the test. Expected outcome:
trigger-testsruns on the emu-access runner andcreate-github-app-tokensucceeds (no 403).sdk-java-isolated-prworkflow_dispatchevent appears ondatabricks-eng/eng-dev-ecosystem.success/failurebased on the dispatched run.NO_CHANGELOG=trueThis pull request and its description were written by Isaac.