actions / actions/actions-runner-controller
Ability to save diagnostic logs from the failed runner
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
To better investigate/collaborate on issues like #342 and https://github.com/actions/runner/issues/971, we'd better have a controller feature that allows us to save diagnostic logs from runners.
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
Start by reading issues #342 and #971 to understand the diagnostic-log failures this feature should address, then inspect the controller entry points that manage runners. Define how logs from a failed runner would be captured and saved, and verify the behavior with a failed-runner scenario.
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
- Needs clarification
- Newbie friendliness
- 30/100