ci: add integration tests workflow for Azure and GCP - #463
Closed
Nelson-PROIA wants to merge 1 commit into
Closed
Conversation
- Add integration_tests.yaml that runs on push to main only - Exclude integration tests from test_custom_code.yaml PR workflow - Integration tests require secrets and make real API calls This ensures integration tests run only after merge, not on every PR.
Contributor
Author
|
Closing in favor of properly rescoped work tracked in https://linear.app/mistral-ai/issue/AIR-755/integration-tests-workflow-for-azure-gcp-across-python-typescript-sdks. The Python-only approach here is incomplete — we run integration tests on both Python and TypeScript SDKs, so the workflow needs to be added to both repos consistently. Sub-tickets:
The pattern in this PR (push-to-main only, skip on PRs to avoid quota waste + external-PR breakage) is correct and will be reused when we redo this properly post-holidays. |
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
1 participant
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
Why
Integration tests make real API calls and require secrets. Running them on every PR:
Now they run only after merge to main, validating released code against live services.
Test plan
After merging, verify in GitHub Actions that the new workflow runs on main push and passes with the required secrets configured.