Option to set max job time out on runner level instead of job level
Open
Nobody has claimed this yet.
enhancement
future
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Describe the enhancement
Currently a job time out can only set on job level. Would help a lot if we can enforce the max time out for a job on the level of the self-hosted runner.
Code Snippet
n/a
Additional information
n/a
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating the runner's existing job-timeout handling and configuration path, then examine how runner-level enforcement should interact with job-level timeouts. Done means a self-hosted runner can enforce a maximum timeout for its jobs, with coverage for the relevant behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100