Skip to content
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

Closed
cahillsf opened this issue Dec 11, 2023 · 8 comments
Closed
Labels
area/release Issues or PRs related to releasing triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@cahillsf
Copy link
Member

cahillsf commented Dec 11, 2023

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

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Dec 11, 2023
@cahillsf
Copy link
Member Author

/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)

@k8s-ci-robot k8s-ci-robot added the area/release Issues or PRs related to releasing label Dec 11, 2023
@sbueringer
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 12, 2023
@fabriziopandini
Copy link
Member

fabriziopandini commented Jan 19, 2024

How much frequent is this use case... might copy-pasting a few times is acceptable vs having to maintain something forever

@adityabhatia
Copy link
Contributor

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.

@sbueringer
Copy link
Member

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

@cahillsf
Copy link
Member Author

cahillsf commented Mar 6, 2024

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 ?

@fabriziopandini
Copy link
Member

Thanks for looking into this again
We can eventually reopen/create a new issue in the future if conditions change

/close

@k8s-ci-robot
Copy link
Contributor

@fabriziopandini: Closing this issue.

In response to this:

Thanks for looking into this again
We can eventually reopen/create a new issue in the future if conditions change

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release Issues or PRs related to releasing triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Development

No branches or pull requests

5 participants