You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/08/22 18:46:33 UTC

[GitHub] [beam] dannymartinm commented on a diff in pull request #22703: [GitHub Actions] Self-hosted runners migration

dannymartinm commented on code in PR #22703:
URL: https://github.com/apache/beam/pull/22703#discussion_r951789086


##########
.github/ACTIONS.md:
##########
@@ -17,10 +17,73 @@
     under the License.
 -->
 
-> **PLEASE update this file if you add new github action or change name/trigger phrase of a github action.**
+> **PLEASE update this file if you add new GitHub Action or change name/trigger phrase of a GitHub Action.**
 
-## Beam Github Actions
+## Beam GitHub Actions
 
+Currently, we have both GitHub-hosted and self-hosted (GCP cloud) runners for running the GitHub Actions workflows. The majority of our workflows that run in Ubuntu and Windows run in self-hosted runners, except for those that runs on MacOS and the `Monitor Self-Hosted Runners Status` workflow that monitors our GCP self-hosted runners.

Review Comment:
   A new section `About GitHub Actions Runners and Self-hosted Runners`  is added. It includes the GitHub definition of both `GitHub-hosted` and `Self-hosted` runners for more clarification. Please let us know if it's fine or if more details need to be added. Thanks! 



-- 
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: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org