gaogaotiantian opened a new pull request, #56783: URL: https://github.com/apache/spark/pull/56783
### What changes were proposed in this pull request? Add a unified entry for all scheduled CIs for branch-3.5 (`branch35_scheduler.yml`). It uses `gh workflow` to trigger the self-contained build workflows on `branch-3.5`, and removes the per-build `build_branch35*.yml` files from `master`. This follows the same approach as SPARK-56990 (#56046) for `branch-4.x`, SPARK-57327 (#56379) for `branch-4.1`, and SPARK-57483 (#56530) for `branch-4.0`. SPARK-57621 (#56679) already laid the ground on `branch-3.5` by making the build workflows self-contained and dispatchable, so this PR only needs to change the `master` scheduled tasks. The scheduler triggers the following targets on `branch-3.5` (also exposed via `workflow_dispatch`): `build_scala213`, `build_python_3.9`. The cron schedule preserves the original `0 11 */4 * *` time and `*/4` frequency from the `build_branch35*.yml` files (both builds shared `0 11`, as before). `README.md` is updated so the branch-3.5 badges point at the self-contained workflows filtered by `?branch=branch-3.5`. ### Why are the changes needed? This is part of decoupling our CIs. All `branch-3.5` related CIs should only rely on files on `branch-3.5`, with the exception of this new scheduler file which is needed on `master` to 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_dispatch` once 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. -- 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]
