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

testgrid should support non-GCS stores for test results #7960

Closed
dims opened this issue May 8, 2018 · 16 comments
Closed

testgrid should support non-GCS stores for test results #7960

dims opened this issue May 8, 2018 · 16 comments
Labels
area/testgrid lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@dims
Copy link
Member

dims commented May 8, 2018

Can we please add support for things other than GCS buckets?

  • plain old browsable web directories (http/https)
  • S3 style object stores
    etc..
@dims
Copy link
Member Author

dims commented May 8, 2018

cc @thockin @BenTheElder

@BenTheElder
Copy link
Member

cc @michelle192837 @rmmh
I believe the plan is to open source testgrid including the update which @fejta has also worked on but I'm not sure where these efforts are at currently.

@fejta
Copy link
Contributor

fejta commented May 8, 2018

/area testgrid
/help

This sounds like a great task for someone outside of Google to take on!

@k8s-ci-robot k8s-ci-robot added area/testgrid help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels May 8, 2018
@BenTheElder BenTheElder changed the title testgrid should support non-GCE stores for test results testgrid should support non-GCS stores for test results May 9, 2018
@BenTheElder
Copy link
Member

this would be the OSS updater which scrapes the results, though we're not migrated to this one yet.

@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 Aug 7, 2018
@akutz
Copy link
Member

akutz commented Aug 8, 2018

/remove-lifecycle stale

Hi @BenTheElder,

Is the OSS updater still the appropriate location to which to add support for non-GCS storage? Or has Spyglass superseded that? I was thinking of taking on the task of adding S3 support to the updater either directly or via the Go Cloud Project.

@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 Aug 8, 2018
@BenTheElder
Copy link
Member

Spyglass is unrelated to testgrid. (they consume the same data but do different things, sypglass is targeted more at what gubernator job viewing does). I'll defer to @michelle192837 @fejta for testgrid.

@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 Nov 6, 2018
@michelle192837
Copy link
Contributor

/remove-lifecycle stale

This is blocked on open sourcing.

@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 Nov 6, 2018
@midnightconman
Copy link
Contributor

Can we have an update on this @michelle192837?

@michelle192837
Copy link
Contributor

Yup, though not a clear one. This is still blocked on open sourcing, and I don't have a good ETA at the moment for it. :( You probably want to track #10409, #3323, and/or #3324 for when I've got better updates on this.

@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 30, 2019
@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 May 30, 2019
@michelle192837
Copy link
Contributor

/remove-lifecycle rotten
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels May 30, 2019
@spiffxp
Copy link
Member

spiffxp commented Aug 15, 2019

FWIW, we're moving on open sourcing. It'll take a bit before we're in a position to accept contributions and see those land in testgrid.k8s.io, but we're getting there #10409 (comment)

@spiffxp
Copy link
Member

spiffxp commented Aug 15, 2019

/remove-help
I'm going to remove help since this is blocked at the moment, we should add back when it's feasible for a new contributor to accomplish

@k8s-ci-robot k8s-ci-robot removed the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Aug 15, 2019
@dims dims closed this as completed Apr 13, 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.
Projects
None yet
Development

No branches or pull requests

9 participants