Hi all,
Heads-up on a CI change that affects everyone opening PRs from a fork.
*What changed*
PRs from a fork to master now run Java CI on the author's fork, using the
fork's own GitHub Actions runners, instead of the shared ASF runner pool.
Upstream only runs the lightweight checks (PR title, license, source
validation). This takes most of the load off the ASF runners, which we
share with every other ASF project and where our jobs often sit in the
queue.
The full suite still runs on ASF runners before anything lands: master is
now merged through a merge queue, which tests each PR against the latest
master plus the PRs queued ahead of it. A PR only merges if that run is
green. Once a PR is in the merge queue, avoid pushing to it. The queue
tests and merges the commits that were queued, so later changes do not go
in on their own; a committer has to re-queue the PR to include them.
*What you need to do (once)*
1. In your fork of hudi, open the Actions tab and enable workflows. (refer
to screenshot below)
2. Sync your fork and rebase your branch onto the latest upstream master, so
it carries the current CI workflows.
3. Push to your branch. Each push now triggers Java CI on your fork.
[image: image.png]
If your PR's CI looks stuck and never turns green, Actions is most likely
not enabled on your fork. The PR's "CI (fork)" check says "Enable CI on
your fork" in that case. After enabling, push again (an empty commit is
fine) to start a run.
*Where to see your CI results*
- On the PR: the "CI (fork)" check mirrors your fork's run and links to it
It refreshes every 15 minutes or so, so it can lag behind the actual run.
- Live status: on the PR page, click your branch name in the header line
("<you> wants to merge N commits into apache:master from <you>:<branch>").
On your branch's latest commit, the status icon shows the run: a yellow dot
while in progress, a green tick or red cross when done. Click it for the
per-job details.
- Or go straight to the Actions tab of your fork. Re-run failed jobs from
there.
Codecov reports still arrive on the PR, about 15 minutes after your fork
run finishes.
*What stays the same*
- PRs to release-* branches and branch-0.x still run the full suite
upstream.
- Azure CI is unchanged.
*For committers*
Merging to master goes through the merge queue: use "Merge when ready" once
the PR is approved, and the queue runs Java CI before merging.
A PR that changes only docs and images skips the test jobs in the queue.
Details are in the "Pull requests from forks" section of
*.github/workflows/README.md* [1]; the tracking issue is *#20471* [2].
Questions and problems are welcome on this thread or on the issue.
Thanks,
Voon
[1]
https://github.com/apache/hudi/blob/master/.github/workflows/README.md#pull-requests-from-forks
[2] https://github.com/apache/hudi/issues/20471