Granted you viewer access, but the broader issue is how we should setup the permissions here. Should we just make everything in that bucket world-readable?

Right now all results are generated from jobs from the public waterfall, but that might not always be the case.

We should at least make sure that the person that started the perf job can see the results.

The following revision refers to this bug:
  https://chromium.googlesource.com/catapult/+/c6434b02c577499932bf7ec31a9d6872c481dca2

commit c6434b02c577499932bf7ec31a9d6872c481dca2
Author: Simon <simonhatch@chromium.org>
Date: Tue Mar 13 01:07:59 2018

Pinpoint - Upload results2 to bucket with more open permissions

This moves uploads to a bucket with public viewing of storage objects
enabled. Eventually we'll need to figure out internal users, but there
are none on Pinpoint for now.

Bug:  chromium:821001 
Change-Id: I599d98fcdcc5f1045a35ff026b22cf406c6c9ccb
Reviewed-on: https://chromium-review.googlesource.com/959618
Reviewed-by: David Tu <dtu@chromium.org>
Commit-Queue: David Tu <dtu@chromium.org>

[modify] https://crrev.com/c6434b02c577499932bf7ec31a9d6872c481dca2/dashboard/dashboard/pinpoint/models/results2_test.py
[modify] https://crrev.com/c6434b02c577499932bf7ec31a9d6872c481dca2/dashboard/dashboard/pinpoint/models/results2.py