lasdf1234 opened a new pull request, #10612:
URL: https://github.com/apache/gravitino/pull/10612
### What changes were proposed in this pull request?
Adds two GitHub Actions workflow files for the maintenance module, following
the same pattern as the existing
flink-integration-test*.yml:
- .github/workflows/maintenance-integration-test.yml — trigger workflow
that fires on push/pull_request to main /
branch-*. Uses dorny/paths-filter to skip runs when no relevant files have
changed. Triggers on changes to
maintenance/** as well as shared modules (api/**, core/**, server/**,
catalogs/**, etc.).
- .github/workflows/maintenance-integration-test-action.yml — reusable
workflow_call action. Checks out the repo,
sets up JDK 17 (Temurin), builds the full distribution, frees disk space,
then runs :maintenance:optimizer:test in
both embedded and deploy modes with -PskipDockerTests=false. On failure (or
when the upload log label is present),
uploads test reports and logs as artifacts.
### Why are the changes needed?
The maintenance module contains integration tests under
org.apache.gravitino.maintenance.optimizer.integration.test.** but had no CI
workflow to execute them. Without CI,
regressions in the maintenance module (optimizer, updaters, jobs) could go
undetected on push or pull request.
Fix: https://github.com/apache/gravitino/issues/10611
### Does this PR introduce any user-facing change?
No. This is a CI-only change adding new workflow files. No APIs,
configuration keys, or runtime behaviour are
affected.
### How was this patch tested?
Workflow syntax validated locally. The action follows the same structure as
the proven
flink-integration-test-action.yml. Integration tests under
:maintenance:optimizer pass when run locally with:
./gradlew -PskipDockerTests=false :maintenance:optimizer:test \
--tests "org.apache.gravitino.maintenance.optimizer.integration.test.**"
--
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]
