[SPARK-58105][INFRA] Remove branch-specific code from build_and_test.yml#57230
Open
gaogaotiantian wants to merge 1 commit into
Open
[SPARK-58105][INFRA] Remove branch-specific code from build_and_test.yml#57230gaogaotiantian wants to merge 1 commit into
gaogaotiantian wants to merge 1 commit into
Conversation
HyukjinKwon
approved these changes
Jul 13, 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
2 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?
Removed all the branch-specific code from build_and_test.yml.
This will only be backported to
branch-4.x, not older branches.Why are the changes needed?
We used to run all the CIs from master and we had to embed branch-specific code in
build_and_test.yml. Now the CIs are decoupled, thebuild_and_test.ymlfile is only used by its own branch. We can drop all thebranch-3.5,branch-4.0andbranch-4.1conditions.As for
branch-4.2, it's not decoupled yet, but the for very few relevant conditions, it behaves exactly the same asbranch-4.xandmaster.Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI.
Was this patch authored or co-authored using generative AI tooling?
No.