Skip to content

Change CI runner from ubuntu-latest to self-hosted#81

Open
vsilent wants to merge 1 commit intomasterfrom
vsilent-patch-1
Open

Change CI runner from ubuntu-latest to self-hosted#81
vsilent wants to merge 1 commit intomasterfrom
vsilent-patch-1

Conversation

@vsilent
Copy link
Copy Markdown
Collaborator

@vsilent vsilent commented Mar 26, 2026

No description provided.

Copilot AI review requested due to automatic review settings March 26, 2026 09:07
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the GitHub Actions CI workflow to run key jobs on self-hosted runners instead of GitHub-hosted ubuntu-latest, presumably to use internal infrastructure and/or reduce hosted runner usage.

Changes:

  • Switch build-and-test job runner from ubuntu-latest to self-hosted.
  • Switch build-release-binaries job runner from ubuntu-latest to self-hosted.
  • Switch docker-build job runner from ubuntu-latest to self-hosted.

build-and-test:
name: Build & Test (features=${{ matrix.features }})
runs-on: ubuntu-latest
#runs-on: ubuntu-latest
Copy link

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keeping the old runs-on line commented out adds noise and can drift from reality. If you want to preserve the previous value, consider removing the commented line and capturing the reasoning in a short comment (or in PR description/docs) instead.

Suggested change
#runs-on: ubuntu-latest
# Run on self-hosted runner (requires project-specific environment, e.g. Docker)

Copilot uses AI. Check for mistakes.
Comment on lines +18 to +19
#runs-on: ubuntu-latest
runs-on: self-hosted
Copy link

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This workflow runs on pull_request, so switching build-and-test to a self-hosted runner will execute untrusted PR code on your own runner machine. Consider using GitHub-hosted runners for PRs (or gating self-hosted runs to trusted events/branches only) to avoid runner compromise and secret exfiltration risks.

Suggested change
#runs-on: ubuntu-latest
runs-on: self-hosted
runs-on: ${{ github.event_name == 'pull_request' && 'ubuntu-latest' || 'self-hosted' }}

Copilot uses AI. Check for mistakes.
Comment on lines +89 to +90
#runs-on: ubuntu-latest
runs-on: self-hosted
Copy link

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

runs-on: self-hosted is very broad; these steps assume a Linux/Ubuntu-like environment (bash conditionals, apt-get, strip). Use runner labels (e.g., runs-on: [self-hosted, linux, x64] and/or a custom label for your prepared image) so the job can’t land on an incompatible self-hosted runner.

Copilot uses AI. Check for mistakes.
Comment on lines +177 to +178
#runs-on: ubuntu-latest
runs-on: self-hosted
Copy link

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR title indicates all jobs should move off ubuntu-latest, but create-release still uses ubuntu-latest in this workflow. Either update the title/scope to reflect the partial migration, or move create-release to the intended runner type as well (keeping in mind any permissions/security requirements).

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants