Add remote execution for package-backed managed tests - #482
Draft
Luc45 wants to merge 3 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.
Summary
--remoteexecution switch torun:activation,run:woo-api, andrun:woo-e2e.Why
The package-backed managed commands now execute locally by default. Callers that need horizontal execution through the Manager still need an explicit, composable route:
--remotechooses where the test runs, while--asyncindependently chooses whether the caller waits.Local ZIPs use the existing upload flow: the CLI uploads the build, enqueues its
upload_id, and the remote worker downloads it before running the package locally. Genericrun:e2eremains local because its blueprints, environments, secrets, volumes, and arbitrary package configuration do not have a lossless remote contract.Behavior
--remote: enqueue through the Manager and wait.--remote --async --json: enqueue and return thetest_run_id.--extension_set: remains implicitly remote for backward compatibility.QIT_TEST_RUN_ID.Validation
RunManagedTestExtensionSetTest: 37 tests, 133 assertions.ExtensionResolverWooVersionTest: 8 tests, 11 assertions.TestPackageManifestTest: 11 tests, 32 assertions.git diff --checkpass.Compatibility note
Remote execution now fails closed when the effective
qit.jsonconfiguration contains unsupported local-only keys. This is intentional: silently ignoring those values could run a different test plan remotely.