actions / actions/actions-runner-controller
Runner-level timeout-minutes config
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
What would you like added?
I'd like to have a variable to set the maximum amount of time (in minutes) the runner will run any job before timing out.
Why is this needed?
At a job level, GitHub provides the timeout-minutes keyword, but in a large organization this is tedious to implement and difficult to enforce.
I'd like a similar keyword at the runner-level so that all jobs across my organization will have this limit instead of the default limit (which seems to be 6 hours) which currently uses up resources for too long.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named in the issue. Start by examining how this controller configures runners and how GitHub Actions applies job-level timeout-minutes; determine whether a runner-level limit is supported, then define a configuration path and verify that the limit applies to every job before the runner timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100