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

Private and shared online results #170

Closed
GoogleCodeExporter opened this issue May 19, 2015 · 3 comments
Closed

Private and shared online results #170

GoogleCodeExporter opened this issue May 19, 2015 · 3 comments
Labels
status: fixed type=defect Bug, not working as expected
Milestone

Comments

@GoogleCodeExporter
Copy link

Currently online results uploaded to http://microbenchmarks.appspot.com are 
publicly available. Would it be possible to restrict access to them so that 
only uploading person can see them? I don't want to publish my microbenchmarks. 
Ability to mark subset of benchmarks and publishing them while others remain 
private would be even better.

Once this is done, how can several people (team) share the results, while 
anonymous users can't access them? By sharing an API private key?

Original issue reported on code.google.com by nurkiew...@gmail.com on 18 Aug 2012 at 1:38

@GoogleCodeExporter
Copy link
Author

Original comment by gak@google.com on 29 Oct 2012 at 5:44

@GoogleCodeExporter
Copy link
Author

Original comment by gak@google.com on 1 Nov 2012 at 9:21

  • Added labels: Milestone-1.0

@GoogleCodeExporter
Copy link
Author

In the new sharing model for the webapp, Caliper results are now accessible by 
anyone with the link, but the link itself is unguessable.  So, there is no 
public index of results and they'll never be discoverable, but you also can't 
strictly deny access.  We believe that this model will be useful for most 
people.  If somebody wants truly private results, the source code for the 
webapp will be pushed soon and hosting a separate instance of the web UI will 
be the recommended solution.

Original comment by gak@google.com on 11 Apr 2013 at 10:46

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: fixed type=defect Bug, not working as expected
Projects
None yet
Development

No branches or pull requests

2 participants