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

open source testgrid dashboard, written in golang #3324

Closed
spiffxp opened this issue Jul 5, 2017 · 25 comments
Closed

open source testgrid dashboard, written in golang #3324

spiffxp opened this issue Jul 5, 2017 · 25 comments
Assignees
Labels
area/testgrid lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Milestone

Comments

@spiffxp
Copy link
Member

spiffxp commented Jul 5, 2017

No description provided.

@fejta
Copy link
Contributor

fejta commented Sep 30, 2017

/assign @rmmh
/unassign @michelle192837

@k8s-ci-robot k8s-ci-robot assigned rmmh and unassigned michelle192837 Sep 30, 2017
@spiffxp spiffxp modified the milestones: 2017-goals, v1.9 Oct 20, 2017
@spiffxp spiffxp modified the milestones: v1.9, 2018-goals Jan 2, 2018
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 2, 2018
@BenTheElder
Copy link
Member

AFAIK this is still ongoing
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 2, 2018
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 1, 2018
@BenTheElder
Copy link
Member

BenTheElder commented Jul 1, 2018 via email

@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 1, 2018
@michelle192837
Copy link
Contributor

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 1, 2018
@spiffxp
Copy link
Member Author

spiffxp commented Aug 1, 2018

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Aug 1, 2018
@michelle192837
Copy link
Contributor

This is still in progress; I'm actively working on it, and will update when the code is in a state to be open sourced (though it will need approval and validation after that before actually being publicly-viewable).

@michelle192837
Copy link
Contributor

Not much to say, but progress has been made on this and it is still chugging along.

@spiffxp
Copy link
Member Author

spiffxp commented Sep 28, 2018

/milestone v1.13

@k8s-ci-robot k8s-ci-robot modified the milestones: 2018-goals, v1.13 Sep 28, 2018
@rdrgmnzs
Copy link
Contributor

Any more progress on this? Would love to have access to it for internal use.

@stevekuznetsov
Copy link
Contributor

@michelle192837 is there any way for this to have a more granular progress bar that we could check ourselves without bugging you?

@michelle192837
Copy link
Contributor

Heya! Sorry about the lack of updates; this is slowly moving through bureaucracy internally, so I don't want to say much until I can say if it's approved for open sourcing officially. That said, while it's working its way through approvals I am still doing some other stuff to make sure it's ready for open sourcing to minimize approval -> release time.

Once approved, I'll update here, and there should be more publicly-visible progress I can give. ^^

@stevekuznetsov
Copy link
Contributor

OK, sounds good! Just wanted to check if there was something easier than bugging you for updates :)

@michelle192837
Copy link
Contributor

Nah, feel free to bug me for updates. ^^ But I'll try and make it so you don't have to as often.

@spiffxp
Copy link
Member Author

spiffxp commented Jan 3, 2019

/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

@spiffxp
Copy link
Member Author

spiffxp commented Jul 25, 2019

/milestone v1.16
/unassign @rmmh
/assign @michelle192837
to move to whichever milestone is most appropriate

@michelle192837
Copy link
Contributor

michelle192837 commented Jul 25, 2019

Slating this for early next year.

/milestone v1.18
/milestone 2020-goals

ETA: Ah, darn. @spiffxp?

@k8s-ci-robot
Copy link
Contributor

@michelle192837: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

Slating this for early next year.

/milestone v1.18
/milestone 2020-goals

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.

@spiffxp
Copy link
Member Author

spiffxp commented Jul 25, 2019

/milestone 2020-goals

@k8s-ci-robot
Copy link
Contributor

@spiffxp: The provided milestone is not valid for this repository. Milestones in this repository: [2019-goals, someday, v1.16, v1.17]

Use /milestone clear to clear the milestone.

In response to this:

/milestone 2020-goals

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.

@spiffxp
Copy link
Member Author

spiffxp commented Jul 25, 2019

/milestone 2020-goals
can only be in one milestone at a time, I made both of the ones you tried, but am using the less specific one for now

also I think we should use a different team for /milestone in this repo, or get you added to milestone-maintainers

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.16, 2020-goals Jul 25, 2019
@spiffxp spiffxp modified the milestones: 2020-goals, someday Jan 8, 2021
@spiffxp
Copy link
Member Author

spiffxp commented Aug 9, 2021

/sig testing

@k8s-ci-robot k8s-ci-robot added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Aug 9, 2021
@fejta
Copy link
Contributor

fejta commented Aug 10, 2021

@fejta fejta closed this as completed Aug 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testgrid lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Development

No branches or pull requests

9 participants