Run integration test suite against Cloud (discovery) - #2279
Draft
THardy98 wants to merge 19 commits into
Draft
Conversation
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.
This draft adds a dedicated CI job that runs the normal TypeScript integration-test package against the existing ring-0 Temporal Cloud namespace through the envconfig path introduced in #2163. The purpose of this draft is to expose the suite's remaining local-server, privilege, namespace, and consistency assumptions before the permanent blocking check is split into reviewable changes.
The job reuses the Linux x64 debug bridge artifact, builds the workspace with Node 24, and runs the full AVA test glob with
TEMPORAL_TEST_ENV_CONFIG_SERVER=true. It deliberately does not start a local Temporal CLI, so tests that still connect implicitly to localhost fail visibly instead of making the Cloud result look greener than its actual coverage. It uses the repository's existing namespace and API-key credentials, skips fork PRs at the job boundary, and retains TAP output for diagnosis.This draft is expected to be red while failures are classified. It is not intended to merge in that state; remediation will be split into small PRs, after which this job will be rebased and landed as a blocking check.
Part of temporalio/features#851.
Validation: Prettier passes for the workflow. Actionlint reports only the workflow's pre-existing custom-runner, optional-matrix-property, and shell quoting warnings.