TobKed commented on pull request #11877: URL: https://github.com/apache/beam/pull/11877#issuecomment-641137700
After rethinking gh-actions I made some updates which changes CI behavior dependent on the triggering event as presented below: * **on pull_request** - operates on PR branch, builds wheels and uploads them only to gh-action artifacts ([example-run](https://github.com/TobKed/beam/actions/runs/129159523)) * **on push** - operates on master/release/release-candidate branches, build wheels and uploads them gh-action artifacts and GCS bucket (folder - branch name) ([example-run](https://github.com/TobKed/beam/actions/runs/129158855)) * **on schedule** - operates master branch, builds wheels and uploads them to gh-action artifacts and GCS bucket (folder - branch name), tags last commit on master as `nightly-master` ([example-run](https://github.com/TobKed/beam/actions/runs/129288105)) Additionally I've added `Cancel Previous Runs` workflow (`.gihub/workflows/cancel.yml`) which cancels previous runs on the same branch. It was inspired by Apache Airflow solution ([link to PR](https://github.com/apache/airflow/pull/9050)) @aaltay answering your questions: > Could we make it such that: > > * we have a cron job that builds nightly (like a snapshot release) > * and a way to manually trigger this from the release branch, so that the release manager can build wheel files on demand. 1. Nightly is addressed by `on schedule` trigger. 2. I investigated triggering builds manually by using `repository_dispatch` and curl however build triggered by it is executed on master branch and I think there is no convenient way to run it on different branches. If your question is related to "Build Release Candidate" phase it may be solved here as well since build will be triggered during pushing to master/release/release-candidate branches (and related to it by commit hash). WDYT? ---------------------------------------------------------------- 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: us...@infra.apache.org
