-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Improve k8s-triage to be able to create issues in the Cluster API repo #9851
Comments
/area release Sunnatillo expressed interest in working on this, will bring up in release meeting (he is not part of the k8s-sigs so cannot assign directly) |
/triage accepted |
How much frequent is this use case... might copy-pasting a few times is acceptable vs having to maintain something forever |
After looking into this issue quickly and debugging the POST request that the k8s-triage page makes here, the relevant repository information for the respective jobs is not available IIUC. So fixing this issue will require more effort to change request URLs and adjusting the subsequent response properties accordingly here, with the required testing. |
Also in general needs agreement with the folks maintaining k8s-triage. I would recommend opening an issue in test-infra to see if they would be open to a change |
reviewed again in RT meeting today. seems like the effort of implementing/maintaining exceeds the value (echoing Fabrizio's sentiment here: #9851 (comment)). im in favor of closing this issue, WDYT @fabriziopandini / @sbueringer ? |
Thanks for looking into this again /close |
@fabriziopandini: 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. |
Theoretically we can use k8s-triage to generate bug reports for flaky tests via "file bug" (link). Unfortunately the issues are always filed against k/k so we have to manually copy&paste the issue text to a Cluster API repo. Let's see if we can improve k8s-triage to be able to create issues in the Cluster API repo.
Carryover from: #9104
The text was updated successfully, but these errors were encountered: