lostluck opened a new issue, #28604: URL: https://github.com/apache/beam/issues/28604
### What happened? The Cut release branch workflow is described as kicking off the new snapshot build, but actually doesn't successfully do so. The PR to the release branch is written, but the "Run Gradle Publish" comment is happening in the description field, so automation is not triggered. https://github.com/apache/beam/pull/28572 (See for the release-2.51.0 edition). I think if the comment were to be automatically done separately (instead of as part of the pr creation), this would be resolved. cc: @kennknowles @damccorm https://github.com/apache/beam/blob/master/.github/workflows/cut_release_branch.yml#L180 Aside: We should migrate that script to use `gh` instead of hub since it's built into action runners. Avoids installing the `hub` tool, and they serve similar purposes eg. https://github.com/apache/beam/blob/master/.github/workflows/build_release_candidate.yml#L298 ### Issue Priority Priority: 2 (default / most bugs should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [ ] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- 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]
