-
Notifications
You must be signed in to change notification settings - Fork 8
Always use arm64 standard runners #504
Copy link
Copy link
Closed as not planned
Labels
part:ciAffects the GitHub workflow and other parts for running CIAffects the GitHub workflow and other parts for running CIpart:templateAffects the cookiecutter template filesAffects the cookiecutter template filesresolution:invalidThis doesn't seem rightThis doesn't seem righttype:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to users
Milestone
Metadata
Metadata
Assignees
Labels
part:ciAffects the GitHub workflow and other parts for running CIAffects the GitHub workflow and other parts for running CIpart:templateAffects the cookiecutter template filesAffects the cookiecutter template filesresolution:invalidThis doesn't seem rightThis doesn't seem righttype:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to users
What's needed?
When arm64 runners were introduced, standard runners only worked for public repos, so for private repos one had to create their how custom runners.
This introduced some complexity in the CI workflow:
frequenz-repo-config-python/cookiecutter/{{cookiecutter.github_repo_name}}/.github/workflows/ci.yaml
Line 77 in fe49b18
Now GitHub made available the standard arm64 for private repos too.
Proposed solution
Use the new standard arm64 runners always by removing the complicated construction of the
runs-on.Use cases
No response
Alternatives and workarounds
No response
Additional context
No response