voonhous opened a new pull request, #20476: URL: https://github.com/apache/hudi/pull/20476
### Describe the issue this Pull Request addresses Every fork PR runs the full Java CI on the shared ASF runner pool, where it queues behind other ASF projects. With the merge queue as the merge gate, the per-push PR run can move to the contributor's fork, as apache/arrow-rs does. Part of #20471. Stacked on #20473 (the merge queue itself is #20474): review the commits after the merge of #20473's branch. ### Summary and Changelog - `bot.yml` and `java_ci_engines.yml` run on every branch push. On fork PRs to master every test job skips upstream (one route condition per file, as a YAML anchor); the contributor's push runs them on the fork's own runners, and the merge queue runs them on ASF runners before merge. Release-branch PRs and same-repository PRs keep upstream testing. - Each aggregate job accepts skipped jobs only on a fork PR to master, and links the fork's run from its summary. - New `fork_ci_status.yml`, adapted from arrow-rs: mirrors both fork runs onto the PR as one informational `CI (fork)` check, the worse result winning (every 15 minutes, plus after each upstream run). <details> <summary>Smaller changes</summary> - Fork pushes cancel the older run of the same branch; upstream pushes stay keyed by SHA. - 58 node tests of the bridge script and of the routing of every test job in both workflows run in `validate-pr-and-source`. - `.github/workflows/README.md` gains "Pull requests from forks": enable Actions on the fork, rebase onto master, push. </details> ### Impact Contributors need Actions enabled on their fork; until then `CI (fork)` says so. Fork PRs stop using ASF runners until they enter the queue. ### Risk Level medium. The merge gate becomes the merge queue; without it, fork PRs would merge on advisory results only, so this lands after the queue is live. ### Documentation Update `.github/workflows/README.md` updated; the website contribute page follows in an asf-site PR. ### Contributor's checklist - [x] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [x] Enough context is provided in the sections above - [x] Adequate tests were added if applicable -- 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]
