| OLD | NEW |
|---|
| (Empty) |
| 1 ### Updating APKs in this folder (for new milestones, builders, or APKs) | |
| 2 | |
| 3 1. Find the commit as close as possible to the current branch point (i.e. if the | |
| 4 latest builds are m59, we want to compare to the commit before the m58 branch | |
| 5 point). | |
| 6 | |
| 7 2. Download and unzip build artifacts from the relevant perf builder. You can | |
| 8 use this link: | |
| 9 [https<nolink>://storage.cloud.google.com/chrome-perf/**Android%20Builder**/full
-build-linux_**3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a**.zip](https://storage.c
loud.google.com/chrome-perf/Android%20Builder/full-build-linux_3a87aecc31cd1ffe7
51dd72c04e5a96a1fc8108a.zip) | |
| 10 , replacing the bolded parts with your info OR from the | |
| 11 "gsutil upload_build_product" step on the bot page (both are Googlers only). | |
| 12 | |
| 13 3. Upload the apk: _upload_to_google_storage.py --bucket | |
| 14 'chromium-android-tools/apks/**Android_Builder**/**58**' | |
| 15 **path/to/ApkTarget.apk**_ replacing the bolded parts again. | |
| 16 * Note that we use **Android_Builder** instead of **Android Builder** (replace | |
| 17 spaces with underscores) | |
| 18 | |
| 19 4. Move the generated .sha1 file to the corresponding place in | |
| 20 //build/android/binary_size/apks/. In this case, the path would be | |
| 21 //build/android/binary_size/apks/Android_Builder/58 | |
| 22 | |
| 23 5. Commit the added .sha1 files and (optionally) update the `CURRENT_MILESTONE` | |
| 24 in apk_downloader.py | |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2764923002:
Revert of Android: Add APK patch size estimates to resource_sizes.py. (Closed)
