dannymartinm opened a new pull request, #23390: URL: https://github.com/apache/beam/pull/23390
As part of the [Beam Release Process](https://beam.apache.org/contribute/release-guide/), the following PR includes the workflow to run the [verify_release_build.sh](https://github.com/apache/beam/blob/master/release/src/main/scripts/verify_release_build.sh) script described in [step 6. Verify Release Branch - Run automation script](https://beam.apache.org/contribute/release-guide/#run-automation-script-verify_release_buildsh). Files: * Composite action to install GitHub CLI in linux: `.github/actions/setup-gh-cli-linux/action.yml` * Verify Release Workflow: `.github/workflows/verify_release_build.yml` * Script to comment Trigger Phrases in batch in the given Pull Request: `scripts/ci/release/comment_pr_trigger_phrases.sh` * `scripts/ci/release/mass_comment.txt` file where are included the same Trigger Phrases that are in the [mass_comment.py](https://github.com/apache/beam/blob/master/release/src/main/scripts/mass_comment.py) file. * `scripts/ci/release/jenkins_trigger_phrases.txt` where are included the Release Gradle Build job and some PostCommit and PreCommits jobs that will not be migrated to GitHub Actions in the first iteration of the massive migration. `* Note`: Currently, the `verify_release_build` workflow is pointing to the `mass_comment.txt` file when commenting Trigger Phrases as we don't have enabled Trigger Phrases for PostCommit and PreCommit GitHub Actions workflows yet and also, we haven't migrated those jobs. Once there are in place, feel free to update the workflow to call the PostCommits and PreCommits workflows as well as pointing to the `jenkins_trigger_phrases.txt` file which includes some of those jobs that are missing in GitHub Actions. ------------------------ Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily: - [ ] [**Choose reviewer(s)**](https://beam.apache.org/contribute/#make-your-change) and mention them in a comment (`R: @username`). - [ ] Mention the appropriate issue in your description (for example: `addresses #123`), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead. - [ ] Update `CHANGES.md` with noteworthy changes. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). See the [Contributor Guide](https://beam.apache.org/contribute) for more tips on [how to make review process smoother](https://beam.apache.org/contribute/get-started-contributing/#make-the-reviewers-job-easier). To check the build health, please visit [https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md) GitHub Actions Tests Status (on master branch) ------------------------------------------------------------------------------------------------ [](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule) [](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule) [](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule) [](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule) See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more information about GitHub Actions CI. -- 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]
