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

[RFC] Link test pipelines in testgrid with GitHub issues #363

Open
mkorbi opened this issue Feb 10, 2021 · 2 comments
Open

[RFC] Link test pipelines in testgrid with GitHub issues #363

mkorbi opened this issue Feb 10, 2021 · 2 comments

Comments

@mkorbi
Copy link

mkorbi commented Feb 10, 2021

It would be great if it is possible to link a test with a GitHub issue. Right now I'm serving in the Release Team CI Signal, and part of our doing is to look up for the flaky and failing test and raise issues to solve them. We have to manually check if these tests are already addressed in some GitHub issue, this can be inside or outside of our project dashboard.

This would increase the transparency of fixing upcoming issues and brings the testgrid and resolution process closer together.

From an implementation POV the best idea right now would be to extend testgrid by a component that can be configured to read open issues either from organizations and/or project boards. Therefore each pipeline requires a UID that can be addressed maybe within the headline (potentially alpha numeric to keep it short) or within the body of the issue.

@spiffxp
Copy link
Contributor

spiffxp commented Feb 17, 2021

ping @chases2 @michelle192837 who might have some context / input

@michelle192837
Copy link
Collaborator

There is precedent for a component like this; we have one internally but not one in open-source (the code doesn't really carry over given the different issue tracking systems). (I know Triage was mentioned as a potential place to track instead, and I think some combination of the two would be great; Triage and TestGrid can both allow filing bugs with necessary structured info, and display issues linked to particular failures or tests (respectively))

I think we have working on this on a timeline for the latter part of this year, but this would be a good thing for folks to contribute before then (though it'll need some design first). I'm a bit worn out this week in particular so my design hat isn't there, but happy to answer questions and discuss more! ^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants