HyukjinKwon opened a new pull request #32092:
URL: https://github.com/apache/spark/pull/32092
### What changes were proposed in this pull request?
This PR proposes to leverage the GitHub Actions resources from the forked
repositories instead of sharing the resources in ASF.
This is how it works:
1. "Build and test" (`build_and_test.yml`) triggers a build on any commit
on any branch (except `branch-*.*`), which means:
- The original repository will trigger the build on any commits in
`master` branch
- The forked repository will trigger the build on any commit in any
branch.
2. The build triggered in the forked repository will checkout the original
repository's `master` branch locally, and merge the branch from the forked
repository into the original repository's `master` branch locally.
Therefore, the tests in the forked repository will run after sync'ed with
the original repository's `master` branch.
3. In the original repository, it triggers a workflow that detects the
workflow triggered in the forked repository, and add a comment on the PR,
pointing out the workflow.
In short,
1. You create a PR, your repository triggers the workflow. It uses the
resources allocated to you.
2. Apache Spark repository finds your workflow, and add it as a comment in
the PR
### Why are the changes needed?
ASF shares the resources across all the ASF projects, which makes the
development slow down.
Please see also:
- Discussion in the [email protected] mailing list:
https://lists.apache.org/x/thread.html/r48d079eeff292254db22705c8ef8618f87ff7adc68d56c4e5d0b4105@%3Cbuilds.apache.org%3E
- Infra ticket: https://issues.apache.org/jira/browse/INFRA-21646
By distributing the workflows to use author's resources, we can get around
this issue.
### Does this PR introduce _any_ user-facing change?
No, this is a dev-only change.
### How was this patch tested?
Manually tested at https://github.com/HyukjinKwon/spark/pull/34 and
https://github.com/HyukjinKwon/spark/pulls/33.
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
