New issue
Advanced search Search tips

Issue 904440 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Feature

Blocking:
issue 903845
issue 903847


Show other hotlists

Hotlists containing this issue:
CrOSParallelCQ


Sign in to add a comment

Transition to new Google Crash symbol upload API endpoint

Project Member Reported by jclinton@chromium.org, Nov 12 
Currently, we are updating an IP whitelist to enable upload of Crash symbols during builds. The Crash team is launching a new One Platform API endpoint to perform these uploads at the end of Q1. Once this is done, IP whitelisting will no longer be required. This item tracks uploading to the new API endpoint.

Comment 1 by vapier@google.com, Nov 12 

off the top of my head, the only code that communicates with the google crash symbol system is chromite/scripts/upload_symbols.py, so shouldn't be too painful to adjust

Comment 2 by dgarr...@chromium.org, Nov 12 

There was some brief discussion about a new API that lets us upload a tarball (perhaps via GS URI) instead of individual symbol files. That would save us about an hour per build, and get rid of almost all of the flake problems (at least on our side).

Comment 3 by jclinton@chromium.org, Nov 13

Labels: Disable-Nags

Comment 4 by jclinton@chromium.org, Nov 13 

Google Crash team tracking bug at https://b.corp.google.com/issues/80337428
►

Sign in to add a comment