gaogaotiantian opened a new pull request, #57319: URL: https://github.com/apache/spark/pull/57319
### What changes were proposed in this pull request? This PR makes the remaining `branch-4.2` scheduled build workflow files self-contained, following the same approach as the `branch-4.1` work (SPARK-57267) and SPARK-57115 (which did this for `build_java17.yml`): - Rewrites `build_java21.yml`, `build_java25.yml`, `build_maven.yml`, `build_maven_java21.yml`, `build_non_ansi.yml`, `build_python_3.11.yml`, and `build_python_3.14.yml` so they are triggered by `workflow_dispatch` only (the dormant `schedule:` triggers are removed; scheduled runs on a non-default branch never fire anyway), drop the inherited `branch: master` (so they build `branch-4.2`), and use generic, non-branch-tagged names. The per-build configurations are relocated from the active `build_branch42_*.yml` files on `master` so the coverage matches what `branch-4.2` schedules today. Notes: - `build_and_test.yml` defaults `branch` to `branch-4.2`, so those callers omit `branch`. `maven_test.yml` defaulted `branch` to `master`, so this PR bumps that default to `branch-4.2` (matching `build_and_test.yml`); with the default fixed, `build_maven.yml` / `build_maven_java21.yml` no longer need an explicit `branch: branch-4.2`. - `build_non_ansi.yml` picks up the `branch-4.2` config from `build_branch42_non_ansi.yml` (Python 3.11 image, no bloom-filter env, `build-core-utils: false`, no `pyspark-pandas`). A pre-existing invalid trailing comma in the non-ANSI `envs` JSON was fixed during relocation. - `build_java17.yml` is already self-contained (SPARK-57115) and is left unchanged. ### Why are the changes needed? This is the `branch-4.2` side of decoupling our scheduled CIs (cf. the `branch-4.1` and `branch-4.x` efforts). Scheduled workflows only fire from the default branch, so `branch-4.2` CI should consist of self-contained, dispatchable workflow files on `branch-4.2` that a single scheduler on `master` can trigger. This PR prepares those targets; a follow-up on `master` will add the scheduler and remove the `build_branch42_*.yml` files. ### Does this PR introduce _any_ user-facing change? No. CI only. ### How was this patch tested? These workflows can be triggered manually via `workflow_dispatch` once merged. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 4.8) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
