[SPARK-58538][INFRA] Add branch-4.3 CI scheduler and release integration - #57741
Open
HeartSaVioR wants to merge 1 commit into
Open
[SPARK-58538][INFRA] Add branch-4.3 CI scheduler and release integration#57741HeartSaVioR wants to merge 1 commit into
HeartSaVioR wants to merge 1 commit into
Conversation
Add the CI and release plumbing that `master` maintains for each active release branch, for the newly cut `branch-4.3`: - add `.github/workflows/branch43_scheduler.yml`, modelled on `branch42_scheduler.yml`, dispatching the eight per-branch build workflows against `--ref branch-4.3`; - add `branch-4.3` to both branch lists in `publish_snapshot.yml` (the `workflow_dispatch` input default and the strategy matrix default, which the file marks as needing to stay in sync); - add a `branch-4.3` badge row to `README.md`, following the release-branch pattern (which includes `build_main.yml`, unlike the rolling `branch-4.x`). Cron hours are staggered against the existing schedulers to spread runner load: branch-4.3 uses 0, 1, 6, 8, 10, 14, 20 and 23 UTC. `dev/create-release/release-util.sh` needs no change: it derives the latest release branch by excluding `master` and `branch-4.x` and taking the highest remaining, which already resolves to `branch-4.3`. Co-authored-by: Isaac
zhengruifeng
approved these changes
Aug 4, 2026
uros-b
approved these changes
Aug 4, 2026
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
3 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.
What changes were proposed in this pull request?
Add the CI and release plumbing that
mastermaintains for each active release branch, for the newly cutbranch-4.3:.github/workflows/branch43_scheduler.yml, modelled onbranch42_scheduler.yml, dispatching the eight per-branch build workflows against--ref branch-4.3;branch-4.3to both branch lists inpublish_snapshot.yml(theworkflow_dispatchinput default and the strategy matrix default, which the file marks as needing to stay in sync);branch-4.3badge row toREADME.md, following the release-branch pattern (which includesbuild_main.yml, unlike the rollingbranch-4.x).Cron hours are staggered against the existing schedulers to spread runner load: branch-4.3 uses 0, 1, 6, 8, 10, 14, 20 and 23 UTC.
dev/create-release/release-util.shneeds no change: it derives the latest release branch by excludingmasterandbranch-4.xand taking the highest remaining, which already resolves tobranch-4.3.Why are the changes needed?
Since we cut the branch for 4.3, we need to setup new CI schedule for this branch.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI schedule will confirm.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 5