open source testgrid updater, written in golang
Closed this issue · 16 comments
/unassign @Q-Lee
/assign @michelle192837
per sig-testing v1.9 roadmap
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
/remove-lifecycle stale
This has been worked on https://github.com/kubernetes/test-infra/tree/master/testgrid/cmd/updater
/milestone 1.12
Is this in use today? I see https://github.com/kubernetes/test-infra/blob/master/testgrid/cluster/updater_deployment.yaml
/milestone v1.13
This mostly exists but isn't in use. Waiting on the filtering/grouping logic that lives in the frontend to be released so we can write the summarizer.
That is in progress still; tracking the overall work in #3324, but if that hits a roadblock will look at separating that out for use with the existing updater.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
/lifecycle frozen
/milestone 2019-goals
It sure would be nice if we could do this in v1.14, but I'm going to defer to @michelle192837 to add back in to v1.14 milestone
Let's have this in the v1.17 milestone?
@fejta: 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.