[SPARK-58242][INFRA] Move scheduled CIs for 4.2 to branch-4.2#57408
Closed
gaogaotiantian wants to merge 1 commit into
Closed
[SPARK-58242][INFRA] Move scheduled CIs for 4.2 to branch-4.2#57408gaogaotiantian wants to merge 1 commit into
gaogaotiantian wants to merge 1 commit into
Conversation
Add a unified entry for all scheduled CIs for branch-4.2 (`branch42_scheduler.yml`). It uses `gh workflow` to trigger the self-contained build workflows on `branch-4.2`, and removes the per-build `build_branch42_*.yml` files from `master`. Co-authored-by: Isaac
HyukjinKwon
approved these changes
Jul 21, 2026
uros-b
approved these changes
Jul 22, 2026
Member
|
Thank you @gaogaotiantian and @HyukjinKwon! |
dongjoon-hyun
approved these changes
Jul 22, 2026
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
Member
There was a problem hiding this comment.
+1, LGTM. Thank you, @gaogaotiantian and all.
Member
|
Merge Summary:
Posted by |
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
4 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 a unified entry for all scheduled CIs for branch-4.2 (
branch42_scheduler.yml). It usesgh workflowto trigger the self-contained build workflows onbranch-4.2, and removes the per-buildbuild_branch42_*.ymlfiles frommaster.This follows the same approach as SPARK-56990 (#56046) for
branch-4.x, SPARK-57327 (#56379) forbranch-4.1, and SPARK-57483 (#56530) forbranch-4.0. SPARK-58180 (#57319) already laid the ground onbranch-4.2by making the build workflows self-contained and dispatchable, so this PR only needs to change themasterscheduled tasks.The scheduler triggers the following targets on
branch-4.2(also exposed viaworkflow_dispatch):build_java17,build_java21,build_java25,build_maven,build_maven_java21,build_non_ansi,build_python_3.11,build_python_3.14. Note this differs from thebranch-4.1set:branch-4.2has ajava25build but nopython_pypy3.10build. The cron schedule preserves the original times and*/2frequency from thebuild_branch42_*.ymlfiles.README.mdis updated so the branch-4.2 badges point at the self-contained workflows filtered by?branch=branch-4.2.Why are the changes needed?
This is part of decoupling our CIs. All
branch-4.2related CIs should only rely on files onbranch-4.2, with the exception of this new scheduler file which is needed onmasterto trigger scheduled tasks (scheduled workflows only fire from the default branch).Does this PR introduce any user-facing change?
No. CI only.
How was this patch tested?
These workflows can be triggered manually via
workflow_dispatchonce merged.Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 4.8)
This pull request and its description were written by Isaac.