lasdf1234 opened a new issue, #10611:
URL: https://github.com/apache/gravitino/issues/10611
### What would you like to be improved?
### What would you like to be improved?
The maintenance module (:maintenance:optimizer, :maintenance:updaters,
:maintenance:jobs) has integration tests
under org.apache.gravitino.maintenance.optimizer.integration.test.**, but
there is no GitHub Actions workflow to run
them on push or pull request. This means regressions in the maintenance
module go undetected in CI.
### How should we improve?
Add two workflow files mirroring the existing flink-integration-test*.yml
pattern:
- 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 paths changed
(maintenance/**, api/**, core/**, server/**, etc.),
and delegates to the action workflow via MaintenanceIT-on-push /
MaintenanceIT-on-pr jobs.
- maintenance-integration-test-action.yml — reusable workflow_call action
that checks out, sets up JDK 17, builds
the distribution, then runs :maintenance:optimizer:test in both embedded and
deploy modes with
PskipDockerTests=false. On failure (or when the upload log label is set),
uploads logs and reports as artifacts.
### How should we improve?
_No response_
--
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]
