-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write a GitHub Issue Gatherer to link issues to tests in TestGrid #10701
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
I'm currently working on a solution for this feature. It consists of three parts described briefly in the readme, but the idea is as follows: Part 1: "GitHub Issue Scraper": get data from GitHub API to a gostruct:
Part 2: "Target Identifier": get data from that struct to this struct/proto: issue_state.pb.go Part 3: Write the proto so that TestGrid can consume it |
/remove-help |
A new controller that pins together issues and test targets Issue kubernetes#10701
A new controller that pins together issues and test targets Issue kubernetes#10701
A new controller that pins together issues and test targets Issue kubernetes#10701
A new controller that pins together issues and test targets Issue kubernetes#10701
A new controller that pins together issues and test targets Issue kubernetes#10701
A new controller that pins together issues and test targets Issue kubernetes#10701
A new controller that pins together issues and test targets Issue kubernetes#10701
A new controller that pins together issues and test targets Issue kubernetes#10701
A new controller that pins together issues and test targets Issue kubernetes#10701
A new controller that pins together issues and test targets Issue kubernetes#10701
/assign |
A new controller that pins together issues and test targets Issue kubernetes#10701
A new controller that pins together issues and test targets Issue kubernetes#10701
A new controller that pins together issues and test targets Issue kubernetes#10701
/milestone v1.16 |
Correct! Sean's done a lot of the work to do this, need a few more adjustments to actually have it run and used. |
pin: maintenance-ci-testgrid-config-upload |
The pin is being picked up by Entomologist, and is now showing up on Testgrid There are many more enhancements to this process that can be made, but the feature is in place. |
@chases2: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
With issue_state.proto out, it's now possible to write a tool that crawls GitHub issues for issues that mention a failing test, and write the info about that issue such that TestGrid can read it! (Or rather, it's ALMOST possible; this requires a small change internally as well to pick up the issue_state proto itself when updating dashboards).
Tagging this 'help-wanted' as it's a feature that 1) I currently don't have bandwidth for, but 2) a helpful contributor could tackle if they're so inclined. ^^ Feel free to ask questions or discuss the design for such a tool.
This should come with a proposal for a change in config.yaml for a more useful file_bug_template, so people monitoring TestGrid dashboards can easily manually-file a bug when a failure occurs, and that bug can be linked to the failing test.
/area testgrid
/help
The text was updated successfully, but these errors were encountered: