Repository navigation
Conversation
mogita
changed the title
This branch has not been deployed
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.
Problem
The scheduled tests fail before and during the test run. They use the JDK preinstalled on the runner, and
ubuntu-latestnow ships Java 25, which Gradle 8.4 cannot run on. They also do not pass the multi-tenant app credentials, soTeamUsageStatsIntegrationTestfails at initialization.Solution
The workflow sets up Java 11 with the same step the Build workflow uses, and passes
STREAM_MULTI_TENANT_KEYandSTREAM_MULTI_TENANT_SECRETthe same way.How to verify
Note
Low Risk
CI workflow-only change; no application runtime or production behavior affected.
Overview
The Scheduled tests workflow no longer relies on the runner’s default JDK (now incompatible with Gradle 8.4). It pins Java 11 via
actions/setup-java@v4with Corretto, matching the main CI build job.The Run tests step now injects
STREAM_MULTI_TENANT_KEYandSTREAM_MULTI_TENANT_SECRETso integration tests that need multi-tenant Stream credentials can initialize, using the same vars/secrets fallback pattern as CI.Reviewed by Cursor Bugbot for commit 0cd0de8. Bugbot is set up for automated code reviews on this repo. Configure here.