[SPARK-56990][INFRA] Move scheduled CIs for 4.x to branch-4.x#56046
Open
gaogaotiantian wants to merge 4 commits into
Open
[SPARK-56990][INFRA] Move scheduled CIs for 4.x to branch-4.x#56046gaogaotiantian wants to merge 4 commits into
gaogaotiantian wants to merge 4 commits into
Conversation
HyukjinKwon
approved these changes
May 21, 2026
dongjoon-hyun
approved these changes
May 21, 2026
dongjoon-hyun
changed the title
Member
|
I removed |
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 a unified entry for all scheduled CIs for 4.x. It will use
gh workflowto trigger actions onbranch-4.x.Why are the changes needed?
This is the prototype effort to decouple our CIs. All
branch-4.xrelated CIs should only rely on files onbranch-4.x, with the exception of the new workflow file which is needed on master to trigger scheduled tasks.We started on 4.x because it's not a maintenance release now and it's very close to master so it's acceptable if the CI was a bit bumpy for a few days. After it stabilizes, we can do the same thing for the maintenance branches.
Does this PR introduce any user-facing change?
No. CI only.
How was this patch tested?
We have to trigger it manually to test it out.
Was this patch authored or co-authored using generative AI tooling?
No.