Update workflow to use self-hosted runners #2
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.
We have optimized GitHub Runners to enhance resource utilization and efficiency by reducing the default packages loaded by runners. Introducing new runner groups for better customization and performance
Note: New runners are deployed as minimal environments without pre-installed software like .NET. You'll need to install any required dependencies within your workflow.
For example: Following code snippet installs dotnet v3.1. For more information visit https://github.com/actions/setup-dotnet
For more information checkout https://betssongroup.atlassian.net/wiki/spaces/TTM/pages/428605820/Transition+repositories+to+new+dedicated+runner+group
New runners include labels for example:
self-hosted
X64
Linux
d-s
default-standard
self-hosted
X64
Linux
d-l
default-large
The assignment of runners depends not only on these labels but also based on the repository's association with specific runner groups and corresponding github apps managed by the CloudOps team.