GitHub user Yicong-Huang added a comment to the discussion: Adopt a UCI-sponsored self-hosted GitHub Actions runner
Thanks @sshiv012 for bringing these context! We want to keep using Github Action workflows to manager our CI and it should be straightforward to configure self-hosted runners. Thanks for confirming the experience from AsterixDB side. Regarding the two notes: 1. security issue, yes I am fully aware of these. Thus in my proposal we want to keep `Fork PRs → ubuntu-latest` with the default runners, and only route trusted jobs to self-hosted runners. We need to pay additional attention to the UCI network and minimal credentials, thanks for the reminder! 2. staging env, actually, we have an ongoing effort led by @Ma77Ball and we are already testing it. The idea is to have 1 staging env for main (dev branch) and 1 staging server for an active release branch (e.g., release/v1.2). @Ma77Ball please share more details and link to references. GitHub link: https://github.com/apache/texera/discussions/6973#discussioncomment-17817981 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
