chore(ci): trim the CI matrix and reset required checks to unblock PRs - #19514
Merged
Conversation
yihua
marked this pull request as ready for review
August 4, 2026 22:50
hudi-agent
reviewed
Aug 4, 2026
hudi-agent
left a comment
hudi-agent
left a comment
Contributor
There was a problem hiding this comment.
Thanks for working on this! This PR trims the CI matrix to bring runner usage back within ASF policy and resets required checks; the only change in the reviewed file is a documentation comment in hudi-integ-test/pom.xml noting that the integ2 suite is currently parked. No issues flagged from this automated pass — a Hudi committer or PMC member can take it from here for a final review.
cc @yihua
yihua
enabled auto-merge (squash)
August 5, 2026 01:47
wombatu-kun
reviewed
Aug 5, 2026
wombatu-kun
reviewed
Aug 5, 2026
4 tasks
auto-merge was automatically disabled
August 5, 2026 09:55
Pull request was closed
3 tasks
This was referenced Aug 5, 2026
ASF infra disabled GitHub Actions on apache/hudi over the amount of runner time the full matrix consumed. Cut Java CI down to one configuration per area: one Spark 3.5 lane on Java 11, one Spark 4.2 lane on Java 17, one Flink 2.1 lane, plus bundle validation and integration tests. The jobs and matrix entries this drops are commented out in place and marked [CI-TRIM] so the coverage can be restored once there is a runner budget for it. Reset required_status_checks in .asf.yaml: the per-job contexts are gone, and a new validate-ci-baseline job takes their place so a PR that collected green checks before the trim cannot merge on them.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #19514 +/- ##
============================================
- Coverage 77.17% 76.38% -0.79%
+ Complexity 33948 32391 -1557
============================================
Files 2575 2520 -55
Lines 143397 138985 -4412
Branches 17579 16695 -884
============================================
- Hits 110662 106169 -4493
- Misses 24476 25176 +700
+ Partials 8259 7640 -619
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe the issue this Pull Request addresses
closes #19526, part of the CI improvement epic #19524.
ASF Infra has disabled GitHub Actions on apache/hudi over how much runner time our CI consumes, so nothing can be verified or merged right now. This brings us back within the ASF GitHub Actions policy on both job concurrency and total usage.
The reset of
required_status_checksmoved to #19523, which should merge first: dropping the per-job contexts is what lets anything merge again, including this PR.Summary and Changelog
Java CI now runs one configuration per area: a Spark lane on Java 11, a Spark lane on Java 17, a Flink lane, bundle validation, and integration tests. The jobs and matrix entries this takes out are commented out in place and marked
[CI-TRIM], so any lane can be restored as our runner budget allows.The one
.asf.yamlline left here addsvalidate-ci-baseline, a new do-nothing job defined in this PR, as a required context, so that a PR holding checks from the old matrix cannot merge on them. The context and the job that reports it stay in the same commit. Both should be removed once no pre-trim PR is open.This is an interim measure to get back to green, not a statement about which versions we support. Coverage comes back properly in #19082, which runs a curated core test suite on every Spark version and reserves the full suites for the latest 3.x and 4.x. That gives us broader version coverage than this PR at a fraction of the cost of the old matrix.
Impact
No product code changes. Two coverage gaps worth being explicit about while this is in place:
Both are temporary. #19082 restores the Spark side with core tests per version; a cheap compile-only lane could do the same for the Flink modules and bundles.
Risk Level
low
Mechanical and reversible: every removed line has an exact commented-out counterpart. Verified that both workflows parse, that
actionlintis clean, and that every surviving job renders the same check name as before, since a mismatch would leave a required context pending forever.One sequencing note:
validate-ci-baselinecan only report once Actions is enabled again, so this should merge alongside or after the re-enable.Documentation Update
none
Contributor's checklist