JingsongLi opened a new pull request, #9787: URL: https://github.com/apache/paimon/pull/9787
### Purpose Spark-only and Flink-only changes currently start unrelated engine test workflows, and most jobs compile the entire Maven reactor. This change consolidates 23 workflow files into 12 and selects the affected test groups through one CI entry point. - Route changes centrally, preserving the existing JDK, Scala, and engine test coverage. Spark changes retain core/integration tests and Flink/Spark interoperability coverage while skipping unrelated Flink jobs. Shared or unknown Java changes select all Java suites; unavailable diffs and manual dispatch select full CI. - Keep push validation on every branch, including contributor forks, as well as pull request validation. Cancel superseded PR runs and expose one `CI result` check that rejects failures, cancellations, and unexpected skips. - Build each Java suite and its dependencies with `-pl ... -am`, then test its selected modules without another clean or redundant `test verify`. Limit Python's Java build to the mixed-language test modules and their dependencies. - Isolate Maven caches by test group, JDK, and Scala, retain failed test reports, and normalize CI, publishing, and maintenance names. Publishing commands remain unchanged. The workflow layout, routing rules, and migration from individual required checks to `CI result` are documented in `.github/CI.md`. ### Tests - `python3 -m unittest discover -s tools/ci -p 'test_*.py'`: 26 tests passed, covering routing, mixed changes, PR/push diff boundaries, renames, large diffs, fallback behavior, Maven command coverage, and the final result check. - actionlint 1.7.11, shell syntax checks, and `git diff --check` passed. - Inspected the Maven reactors for all Java matrix entries and the Python Java build. Offline Maven validation stops on locally unavailable `2.2-SNAPSHOT` artifacts; complete Maven builds and the GitHub-hosted test matrix have not yet been verified. -- 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]
