henry3260 opened a new pull request, #11977: URL: https://github.com/apache/gravitino/pull/11977
### What changes were proposed in this pull request? This PR improves the Gravitino server lifecycle used by Python client integration tests. The Gradle `integrationTest` task now uses dedicated `startGravitinoServer` and `stopGravitinoServer` tasks, with `stopGravitinoServer` registered through `finalizedBy` so Gradle attempts to stop the server even when the integration test task fails. This PR also centralizes the `START_EXTERNAL_GRAVITINO` check in `IntegrationTestEnv.use_external_gravitino()` and updates several authorization-related integration tests to reuse that helper. ### Why are the changes needed? The Python client integration test setup already supports using an externally started Gravitino server in CI. However, the server lifecycle logic was still embedded directly inside the `integrationTest` task, and the external-server environment check was duplicated across multiple test classes. Separating start and stop into dedicated Gradle tasks makes the lifecycle easier to understand and safer on failure. Centralizing the environment check also keeps related integration tests consistent. Related to #5820. ### Does this PR introduce _any_ user-facing change? No. This change only affects Python client integration test infrastructure. ### How was this patch tested? - `git diff --check` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
