[SPARK-58459][4.x][INFRA] Manage build_main.yml per-branch instead of gating on github.ref - #57661
Open
gaogaotiantian wants to merge 1 commit into
Open
[SPARK-58459][4.x][INFRA] Manage build_main.yml per-branch instead of gating on github.ref#57661gaogaotiantian wants to merge 1 commit into
gaogaotiantian wants to merge 1 commit into
Conversation
…ng on github.ref ### What changes were proposed in this pull request? Replace the `github.ref`-based job condition in `build_main.yml` on `branch-4.x` with a simple `github.repository != 'apache/spark'` check. Post-merge CI on the `branch-4.x` integration/staging branch is disabled to save resources; since this branch's copy of the workflow is only ever evaluated for pushes to `branch-4.x`, no `github.ref` comparison is needed to express that. ### Why are the changes needed? The other build workflows (e.g. `build_java21.yml`, `build_python_3.11.yml`) are already managed per-branch, diverging in name/schedule/`branch:` between `master` and `branch-4.x`. `build_main.yml` was the exception, encoding branch-specific behavior via a runtime `github.ref` check. Aligning it with the rest keeps each branch's workflow file self-describing. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? N/A. CI-configuration-only change; post-merge CI remains disabled on `branch-4.x` while fork pushes still run. Co-authored-by: Isaac
gaogaotiantian
changed the title
zhengruifeng
approved these changes
Jul 31, 2026
uros-b
approved these changes
Jul 31, 2026
Member
|
Thank you @gaogaotiantian and @zhengruifeng! |
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?
Replace the
github.ref-based job condition inbuild_main.ymlonbranch-4.xwith a simplegithub.repository != 'apache/spark'check. Post-merge CI on thebranch-4.xintegration/staging branch is disabled to save resources; since this branch's copy of the workflow is only ever evaluated for pushes tobranch-4.x, nogithub.refcomparison is needed to express that.Why are the changes needed?
The other build workflows (e.g.
build_java21.yml,build_python_3.11.yml) are already managed per-branch, diverging in name/schedule/branch:betweenmasterandbranch-4.x.build_main.ymlwas the exception, encoding branch-specific behavior via a runtimegithub.refcheck. Aligning it with the rest keeps each branch's workflow file self-describing.Does this PR introduce any user-facing change?
No.
How was this patch tested?
N/A. CI-configuration-only change; post-merge CI remains disabled on
branch-4.xwhile fork pushes still run.Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.8)
This pull request and its description were written by Isaac.