New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 736441 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Request to add GCS credentials to Catapult tryservers

Project Member Reported by erikc...@chromium.org, Jun 23 2017

Issue description

The symbolize_trace script that lives in catapult downloads Chrome symbols from GCS and uses those to symbolize traces. I would like to add a waterfall test for this. This means the bots need to be able to access the gs://chrome-unsigned bucket.

Is this allowed by Infra policy? Presumably some of our bots must have access to these buckets. The following bots will require credentials

https://build.chromium.org/p/tryserver.client.catapult/builders/
Catapult Windows Tryserver
  build78-b1
  build79-b1
Catapult Mac Tryserver
  vm600-m4
Catapult Linux Tryserver
  slave425-c4		
  slave492-c4		
  slave500-c4		
  slave546-c4		
  slave547-c4	
Catapult Android Tryserver 
  build1-b3	
  build37-b4	

https://build.chromium.org/p/client.catapult/builders/
Catapult Windows
  vm114-m3
Catapult Mac
  vm113-m3
Catapult Linux 
  vm600-m3

I've listed all bots we will eventually need. If this is for some reason a lot of work, the only ones we need for my CL:
https://codereview.chromium.org/2950723002/

Are the Mac bots.
 
We already have a GCS credentials for buckets in https://github.com/catapult-project/catapult/blob/master/common/py_utils/py_utils/cloud_storage.py#L32, if you can reuse those buckets to store Chrome symbols, that would probably require the least amount of work IMO.
Status: WontFix (was: Untriaged)
I can do that.

Sign in to add a comment