Hi Damon I find the approach quite interesting, and I agree that if the YML workflow is no longer required when using direct triggers, then Self-Hosted runners are not necessary for those jobs. Are those workflows planned to be removed in the future when the triggers are synced?
On Fri, Dec 9, 2022 at 11:03 AM Damon Douglas via dev <[email protected]> wrote: > Thank you for this information. For Playground Backend and Frontend, are > self-hosted runners no longer needed since we are using Cloud Build? > > *For those who would like more explanation, please see below.* > > Playground is our https://play.beam.apache.org/ that allows us to execute > Apache Beam code snippets in a modern browser. Deployed on Google Cloud, > we develop automation to build container images and other infrastructure > tasks of the backend and frontend code as a result of GitHub pull request > merges. Because we target Google Cloud, we simplify the automation using a > Cloud Build trigger [1]. Cloud Build allows this image building and other > automation tasks as a result of GitHub events such as a pull request or > merge. When INFRA-23956 [2] resolves, code in the Beam repository related > to the Beam playground will send a message to Cloud Build to trigger the > container image build and other related CI/CD events, hence the name "Cloud > Build trigger". Think of Cloud Build as a Google Cloud native GitHub > action-like service that is appropriate when exclusively targeting Google > Cloud. > > References: > > 1. https://cloud.google.com/build/docs/triggers > 2. https://issues.apache.org/jira/browse/INFRA-23956 > > On Fri, Dec 9, 2022 at 6:57 AM Elias Segundo Antonio < > [email protected]> wrote: > >> Hello Apache Beam Team >> >> We’d like to announce that we will start testing GitHub Actions >> Self-Hosted Runners in the Apache Beam Repository. Infrastructure will be >> in place today at 9:30 AM UTC-6 to migrate the first set of workflows from >> GitHub-provided Runners to Self-Hosted (for the time being, only Windows >> and Linux runners are being replaced). >> >> If everything runs smoothly, the following list of workflows is expected >> to be running in Self-Hosted runners by the end of the day: >> >> - Build Playground Backend >> - Build Playground Frontend >> - Go Tests >> - Issue Tagger >> - Java Tests >> - Label PRs >> - Local Env Tests >> - Report Generator >> - PR bot PR Updates >> - PR bot PRs needing attention >> - PR bot update Reviewers >> - Self Assign >> - Stale >> - Triaged on assign >> - Typescript tests >> >> We will be monitoring the behavior of the runners throughout the day; no >> downtime for GitHub Actions workflows is expected since the new workflows >> will be merged incrementally and runners provided by GitHub Actions will >> continue working as normal. However, please don’t hesitate to report if you >> encounter any issues related to the previous workflows list while we test >> the infrastructure. >> >> Regards. >> -- >> >> Elias Edgardo Segundo Antonio (He/Him) | <https://www.wizeline.com/> | >> wizeline.com <https://www.wizeline.com/> >> >> Site Reliability Engineer I >> >> [email protected] | +52 712 2722589 <+52%20712%20272%202589> (m) >> >> Remote Office, Mexico >> >> >> >> >> >> >> >> >> *This email and its contents (including any attachments) are being sent >> toyou on the condition of confidentiality and may be protected by >> legalprivilege. Access to this email by anyone other than the intended >> recipientis unauthorized. If you are not the intended recipient, please >> immediatelynotify the sender by replying to this message and delete the >> materialimmediately from your system. Any further use, dissemination, >> distributionor reproduction of this email is strictly prohibited. Further, >> norepresentation is made with respect to any content contained in this >> email.* > > -- Elias Edgardo Segundo Antonio (He/Him) | <https://www.wizeline.com/> | wizeline.com <https://www.wizeline.com/> Site Reliability Engineer I [email protected] | +52 712 2722589 (m) Remote Office, Mexico -- *This email and its contents (including any attachments) are being sent to you on the condition of confidentiality and may be protected by legal privilege. Access to this email by anyone other than the intended recipient is unauthorized. If you are not the intended recipient, please immediately notify the sender by replying to this message and delete the material immediately from your system. Any further use, dissemination, distribution or reproduction of this email is strictly prohibited. Further, no representation is made with respect to any content contained in this email.*
