[
https://issues.apache.org/jira/browse/FLINK-27076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Pohl updated FLINK-27076:
----------------------------------
Description:
h2. GitHub Documentation
* About self-hosted runners
* Adding self-hosted runners
* Using self-hosted runners in a GitHub Actions workflow
* Security hardening for self-hosted runners
* Autoscaling with self-hosted runners
* Alternative: Approving workflow runs from public forks: Not suitable for
projects with large amounts of contributors (see Slack thread)
h2. Apache Infra
* Infra ML discussion thread from Apache Pekko
* GitHub self-hosted-runners (most-recently updated wiki article)
* GitHub Actions status (last modified on Jun 20, 2021)
.h2 GitHub Runner
* actions/runner
* Closed issue #494
* Feature request
* Draft PR #783 with fix from @ashb
.h2 GitHub Runner Fork from @ashb
* ashb/runner (releases/pr-security-options branch)
* Automated release of custom GitHub runner - Apparently, we need to deploy the
most-recent version of the GitHub runner to avoid having the runner being
rejected by GitHub.
.h2 Apache Flink ML
* GHA migration roadmap (December 16, 2021)
* Notice thread on migration to GitHub Actions (April 4, 2022)
.h2 Miscellaneous
* Apache Pulsar restricts CI runs to reviewed PRs only. Contributors are asked
to create a branch in their fork as well to use GitHub’s runners, instead. The
project itself relies on Apache’s hosted runners. (see related PR)
There is a discussion about it in the follow-ups of this Infra Slack post
There are concerns shared about losing contributors due to the extra work
that’s necessary to set this up.
> Setup runners
> -------------
>
> Key: FLINK-27076
> URL: https://issues.apache.org/jira/browse/FLINK-27076
> Project: Flink
> Issue Type: Sub-task
> Components: Build System / CI
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
>
> h2. GitHub Documentation
> * About self-hosted runners
> * Adding self-hosted runners
> * Using self-hosted runners in a GitHub Actions workflow
> * Security hardening for self-hosted runners
> * Autoscaling with self-hosted runners
> * Alternative: Approving workflow runs from public forks: Not suitable for
> projects with large amounts of contributors (see Slack thread)
> h2. Apache Infra
> * Infra ML discussion thread from Apache Pekko
> * GitHub self-hosted-runners (most-recently updated wiki article)
> * GitHub Actions status (last modified on Jun 20, 2021)
> .h2 GitHub Runner
> * actions/runner
> * Closed issue #494
> * Feature request
> * Draft PR #783 with fix from @ashb
> .h2 GitHub Runner Fork from @ashb
> * ashb/runner (releases/pr-security-options branch)
> * Automated release of custom GitHub runner - Apparently, we need to deploy
> the most-recent version of the GitHub runner to avoid having the runner being
> rejected by GitHub.
> .h2 Apache Flink ML
> * GHA migration roadmap (December 16, 2021)
> * Notice thread on migration to GitHub Actions (April 4, 2022)
> .h2 Miscellaneous
> * Apache Pulsar restricts CI runs to reviewed PRs only. Contributors are
> asked to create a branch in their fork as well to use GitHub’s runners,
> instead. The project itself relies on Apache’s hosted runners. (see related
> PR)
> There is a discussion about it in the follow-ups of this Infra Slack post
> There are concerns shared about losing contributors due to the extra work
> that’s necessary to set this up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
