[
https://issues.apache.org/jira/browse/FLINK-27076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Pohl updated FLINK-27076:
----------------------------------
Description:
Below is a collection of links around the topic of self-hosted runners and the
current state of the GitHub Actions migration efforts in Apache Flink.
h2. GitHub Documentation
* [About self-hosted
runners|https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners]
* [Adding self-hosted
runners|https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners]
* [Using self-hosted runners in a GitHub Actions
workflow|https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow]
* [Security hardening for self-hosted
runners|https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners]
* [Autoscaling with self-hosted
runners|https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners]
* Alternative: [Approving workflow runs from public
forks|https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks]
(not suitable for projects with large amounts of contributors; see [Slack
thread|https://the-asf.slack.com/archives/CBX4TSBQ8/p1640076905230600])
h2. Apache Infra
* [Infra ML discussion thread from Apache
Pekko|https://cwiki.apache.org/confluence/display/INFRA/GitHub+self-hosted+runners]
* [GitHub
self-hosted-runners|https://cwiki.apache.org/confluence/display/INFRA/GitHub+self-hosted+runners]
(most-recently updated wiki article)
* [GitHub Actions
status|https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status]
(last modified on Jun 20, 2021)
h2. GitHub Runner
* [actions/runner|https://github.com/actions/runner]
* [Closed issue #494|https://github.com/actions/runner/issues/494]
* [Feature request|https://github.com/orgs/community/discussions/53430]
* [Draft PR #783|https://github.com/actions/runner/pull/783] with fix from
[@ashb|https://github.com/ashb]
h2. GitHub Runner Fork from [@ashb|https://github.com/ashb]
* [ashb/runner|https://github.com/ashb/runner]
([releases/pr-security-options|https://github.com/actions/runner/compare/main...ashb:runner:releases/pr-security-options]
branch)
* [Automated release of custom GitHub
runner|https://github.com/ashb/runner/blob/main/.github/workflows/sync-with-upstream.yml]
- 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|https://lists.apache.org/thread/vcyx2nx0mhklqwm827vgykv8pc54gg3k]
(December 16, 2021)
* ML: [Notice thread on migration to GitHub
Actions|https://lists.apache.org/thread/438krxbs7y9lg0f009f1hlojqm54y57s]
(April 4, 2022)
* [exp_github_actions
branch|https://github.com/apache/flink/tree/exp_github_actions] in Apache Flink
repo
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|https://github.com/apache/pulsar/pull/17693/files])
** There is a discussion about it in the follow-ups of [this Infra Slack
post|https://the-asf.slack.com/archives/CBX4TSBQ8/p1663346680496919?thread_ts=1661512133.913279&cid=CBX4TSBQ8]
** There are concerns shared about losing contributors due to the extra work
that’s necessary to set this up.
* [Discussion on whether to use
Jenkins|https://lists.apache.org/thread/vs81xdhn3q777r7x9k7wd4dyl9kvoqn4] back
in 2014 (where the Flink community went with Travis out of convenience)
was:
Below is a collection of links around the topic of self-hosted runners and the
current state of the GitHub Actions migration efforts in Apache Flink.
h2. GitHub Documentation
* [About self-hosted
runners|https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners]
* [Adding self-hosted
runners|https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners]
* [Using self-hosted runners in a GitHub Actions
workflow|https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow]
* [Security hardening for self-hosted
runners|https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners]
* [Autoscaling with self-hosted
runners|https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners]
* Alternative: [Approving workflow runs from public
forks|https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks]
(not suitable for projects with large amounts of contributors; see [Slack
thread|https://the-asf.slack.com/archives/CBX4TSBQ8/p1640076905230600])
h2. Apache Infra
* [Infra ML discussion thread from Apache
Pekko|https://cwiki.apache.org/confluence/display/INFRA/GitHub+self-hosted+runners]
* [GitHub
self-hosted-runners|https://cwiki.apache.org/confluence/display/INFRA/GitHub+self-hosted+runners]
(most-recently updated wiki article)
* [GitHub Actions
status|https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status]
(last modified on Jun 20, 2021)
h2. GitHub Runner
* [actions/runner|https://github.com/actions/runner]
* [Closed issue #494|https://github.com/actions/runner/issues/494]
* [Feature request|https://github.com/orgs/community/discussions/53430]
* [Draft PR #783|https://github.com/actions/runner/pull/783] with fix from
[@ashb|https://github.com/ashb]
h2. GitHub Runner Fork from [@ashb|https://github.com/ashb]
* [ashb/runner|https://github.com/ashb/runner]
([releases/pr-security-options|https://github.com/actions/runner/compare/main...ashb:runner:releases/pr-security-options]
branch)
* [Automated release of custom GitHub
runner|https://github.com/ashb/runner/blob/main/.github/workflows/sync-with-upstream.yml]
- 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|https://lists.apache.org/thread/vcyx2nx0mhklqwm827vgykv8pc54gg3k]
(December 16, 2021)
* ML: [Notice thread on migration to GitHub
Actions|https://lists.apache.org/thread/438krxbs7y9lg0f009f1hlojqm54y57s]
(April 4, 2022)
* [exp_github_actions
branch|https://github.com/apache/flink/tree/exp_github_actions] in Apache Flink
repo
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|https://github.com/apache/pulsar/pull/17693/files])
** There is a discussion about it in the follow-ups of [this Infra Slack
post|https://the-asf.slack.com/archives/CBX4TSBQ8/p1663346680496919?thread_ts=1661512133.913279&cid=CBX4TSBQ8]
** 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
>
> Below is a collection of links around the topic of self-hosted runners and
> the current state of the GitHub Actions migration efforts in Apache Flink.
> h2. GitHub Documentation
> * [About self-hosted
> runners|https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners]
> * [Adding self-hosted
> runners|https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners]
> * [Using self-hosted runners in a GitHub Actions
> workflow|https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow]
> * [Security hardening for self-hosted
> runners|https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners]
> * [Autoscaling with self-hosted
> runners|https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners]
> * Alternative: [Approving workflow runs from public
> forks|https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks]
> (not suitable for projects with large amounts of contributors; see [Slack
> thread|https://the-asf.slack.com/archives/CBX4TSBQ8/p1640076905230600])
> h2. Apache Infra
> * [Infra ML discussion thread from Apache
> Pekko|https://cwiki.apache.org/confluence/display/INFRA/GitHub+self-hosted+runners]
> * [GitHub
> self-hosted-runners|https://cwiki.apache.org/confluence/display/INFRA/GitHub+self-hosted+runners]
> (most-recently updated wiki article)
> * [GitHub Actions
> status|https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status]
> (last modified on Jun 20, 2021)
> h2. GitHub Runner
> * [actions/runner|https://github.com/actions/runner]
> * [Closed issue #494|https://github.com/actions/runner/issues/494]
> * [Feature request|https://github.com/orgs/community/discussions/53430]
> * [Draft PR #783|https://github.com/actions/runner/pull/783] with fix from
> [@ashb|https://github.com/ashb]
> h2. GitHub Runner Fork from [@ashb|https://github.com/ashb]
> * [ashb/runner|https://github.com/ashb/runner]
> ([releases/pr-security-options|https://github.com/actions/runner/compare/main...ashb:runner:releases/pr-security-options]
> branch)
> * [Automated release of custom GitHub
> runner|https://github.com/ashb/runner/blob/main/.github/workflows/sync-with-upstream.yml]
> - 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|https://lists.apache.org/thread/vcyx2nx0mhklqwm827vgykv8pc54gg3k]
> (December 16, 2021)
> * ML: [Notice thread on migration to GitHub
> Actions|https://lists.apache.org/thread/438krxbs7y9lg0f009f1hlojqm54y57s]
> (April 4, 2022)
> * [exp_github_actions
> branch|https://github.com/apache/flink/tree/exp_github_actions] in Apache
> Flink repo
> 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|https://github.com/apache/pulsar/pull/17693/files])
> ** There is a discussion about it in the follow-ups of [this Infra Slack
> post|https://the-asf.slack.com/archives/CBX4TSBQ8/p1663346680496919?thread_ts=1661512133.913279&cid=CBX4TSBQ8]
> ** There are concerns shared about losing contributors due to the extra work
> that’s necessary to set this up.
> * [Discussion on whether to use
> Jenkins|https://lists.apache.org/thread/vs81xdhn3q777r7x9k7wd4dyl9kvoqn4]
> back in 2014 (where the Flink community went with Travis out of convenience)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
