Change runner type from self-hosted to general-runner#161
Open
idelcano wants to merge 1 commit intodevelopmentfrom
Open
Change runner type from self-hosted to general-runner#161idelcano wants to merge 1 commit intodevelopmentfrom
idelcano wants to merge 1 commit intodevelopmentfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request: Update GitHub Actions runner tags
Summary
This PR updates the workflow configuration to change the runner label from self-hosted to general-runner.
Note: Some minor whitespace changes in the workflow file were auto-formatted by the GitHub web editor.
Context
Currently, we use the self-hosted tag, which is a default label shared across all custom runners not managed by GitHub. To improve our infrastructure management, we have deployed new virtual machines and need a way to differentiate between them.
Changes
Updated runs-on: self-hosted to runs-on: general-runner in all workflow files.
Why this is necessary
Using general-runner allows us to:
Isolate workloads: Ensure jobs run on the specific VM intended for these tasks.
Granular Control: Avoid resource conflicts with other custom runners using the generic self-hosted tag.
Scalability: Better tracking of runner usage and performance.