envoyproxy/envoy

Make runners configurable in ci

Open

#39,705 opened on Jun 2, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/cienhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

our ci doesnt allow you to change much of the ci itself in a pr, but we do have .github/config.yaml which is intended to allow some types of change - atm you can change the docker container used by ci eg

what would be really helpful is to be able to set the runners - atm the immediate use case is for testing different macos runners - but its come up plenty in other contexts

implementation shouldnt be too hard - but defo requires off-site testing

Contributor guide

Research direction
Examine the .github/config.yaml file and the CI workflow files to understand how the Docker container is configured, then extend that logic to allow runner label configuration. Test locally or via a fork and coordinate with maintainers for off site testing.
Tech stack
cppgithub actions
Domain
ci cddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75