Skip to content

ci: trigger REST integration tests when SEA path is touched [PECO-2945]#315

Open
eric-wang-1990 wants to merge 3 commits intomainfrom
worktree-PECO-2945-sea-rest-ci
Open

ci: trigger REST integration tests when SEA path is touched [PECO-2945]#315
eric-wang-1990 wants to merge 3 commits intomainfrom
worktree-PECO-2945-sea-rest-ci

Conversation

@eric-wang-1990
Copy link
Collaborator

Detect changes under csharp/src/StatementExecution/ and dispatch a second adbc-csharp-pr-test event with databricks_protocol=rest. Applies to both PR-label and merge queue. Thrift tests unaffected. Closes PECO-2945

eric-wang-1990 and others added 3 commits March 6, 2026 18:43
When csharp/src/StatementExecution/ files change, dispatch an additional
adbc-csharp-pr-test event to databricks-driver-test with
databricks_protocol=rest so the SEA/REST test suite runs alongside
the default Thrift tests.

Applies to both PR (label-triggered) and merge queue workflows.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The internal repo reads github.event.client_payload.extra_parameters as a
JSON object and injects it as extraParameters in the test config. Use that
field instead of the incorrect databricks_protocol top-level field.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@eric-wang-1990 eric-wang-1990 added the integration-test Trigger integration tests in internal repo label Mar 7, 2026
@github-actions
Copy link

github-actions bot commented Mar 7, 2026

🚀 Integration tests triggered! View workflow run

@msrathore-db
Copy link
Collaborator

The cloudFetch tests should be triggered for SEA and thrift since they share the same path.

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

Labels

integration-test Trigger integration tests in internal repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants