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

Set up result publishing #5

Open
rabernat opened this issue May 14, 2021 · 1 comment
Open

Set up result publishing #5

rabernat opened this issue May 14, 2021 · 1 comment

Comments

@rabernat
Copy link
Member

As proposed by @nbren12 in #1 (comment), we will be running these tests as a kubernetes cron job. The clusters will need some way to publish their results, likely just a static http endpoint.

How should this work? I see two basic possibilities:

  • Each testing cluster publishes its results to a public bucket in its own cloud storage. With this, write credentials can be packaged into the kubernetes environment.
  • All clusters publish to a central location. This would require some sort of common credentials.

The former certainly seems easier.

We also need to decide what we want to log. It will be important to capture detailed logs from all parts of the stack, as well as performance reports (timing, etc).

@nbren12
Copy link
Contributor

nbren12 commented May 14, 2021

I agree (1) is easier and allows a more federated model. It would be nice to setup some kind of table of badges, we could bake this into our test script, but maybe there is an easier way.

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

2 participants