In order to reduce the size of the Chromium source checkout, Telemetry stores binaries in Cloud Storage. This includes:
Many benchmarks require these files to run, and will fail without them. Set Up Cloud StorageInstall depot_toolsFollow these instructions to install depot_tools. Request Access (for Google partners)Many of the page set archives are in the Authenticate into Cloud StorageSome files in Cloud Storage include data internal to Google or its partners. To run benchmarks that rely on this data, you need to authenticate. Run the command below and follow the instructions for authentication with your corporate account. $ python depot_tools/gsutil.py config When prompted with “ BucketsTelemetry has three Cloud Storage buckets you can put binary data in.
BSD-compatible support binaries should all go into Google wants to avoid legal issues with distributing third-party content, so to be safe, most recordings of websites on the public web go in Upload to Cloud StorageUpload your files into the bucket “chromium-telemetry”Put the target file in the directory you want it to be when downloaded from Cloud Storage, say $ python depot_tools/upload_to_google_storage.py --bucket chromium-telemetry path/to/target A SHA1 file Check the .sha1 files into the repository$ git add path/to/target.sha1 Download from Cloud StorageDownload the file in Pythonfrom telemetry.util import cloud_storage
cloud_storage.GetIfChanged('path/to/target', cloud_storage.PUBLIC_BUCKET) Download the file manually$ python depot_tools/download_from_google_storage.py -s [target.sha1] -b chromium-telemetry |
For Developers > Telemetry: Introduction >