| Wez | aa00d427 | 2018-04-18 21:42:50 | [diff] [blame] | 1 | # Manually updating Chromium to a new Fuchsia SDK |
| 2 | |
| 3 | Normally the Fuchsia SDK dependency is automatically updated to a recent build |
| 4 | on a regular basis, by the [Fuchsia SDK AutoRoll Bot](https://fuchsia-sdk-chromium-roll.skia.org). |
| 5 | |
| 6 | Should you need to manually update the SDK dependency for some reason, then: |
| Wez | fd67b9a0 | 2017-07-20 00:04:31 | [diff] [blame] | 7 | |
| Scott Graham | 131568b | 2017-08-01 17:20:44 | [diff] [blame] | 8 | 1. Check the [Fuchsia-side |
| Aidan Wolter | 7bc61d0 | 2019-01-03 00:56:49 | [diff] [blame] | 9 | job](https://luci-scheduler.appspot.com/jobs/fuchsia/sdk-topaz-x64-linux) |
| Scott Graham | 4e05b6f | 2018-11-09 17:02:04 | [diff] [blame] | 10 | for a recent green archive. On the "SUCCEEDED" link, copy the SHA-1 from the |
| Scott Graham | 131568b | 2017-08-01 17:20:44 | [diff] [blame] | 11 | `gsutil.upload` link of the `upload fuchsia-sdk` step. |
| Aidan Wolter | 7bc61d0 | 2019-01-03 00:56:49 | [diff] [blame] | 12 | 0. Put that into Chromium's src.git `build/fuchsia/linux.sdk.sha1`. |
| Scott Graham | 131568b | 2017-08-01 17:20:44 | [diff] [blame] | 13 | 0. `gclient sync && ninja ...` and make sure things go OK locally. |
| 14 | 0. Upload the roll CL, making sure to include the `fuchsia` trybot. Tag the roll |
| 15 | with `Bug: 707030`. |
| Wez | fd67b9a0 | 2017-07-20 00:04:31 | [diff] [blame] | 16 | |
| Scott Graham | d83cbaf | 2017-08-16 07:55:08 | [diff] [blame] | 17 | If you would like to build an SDK locally, `tools/fuchsia/local-sdk.py` tries to |
| 18 | do this (so you can iterate on ToT Fuchsia against your Chromium build), however |
| 19 | it's simply a copy of the steps run on the bot above, and so may be out of date. |
| Scott Graham | c050551 | 2017-08-22 02:36:10 | [diff] [blame] | 20 | |
| 21 | In order to sync a Fuchsia tree to the state matching an SDK hash, you can use: |
| 22 | |
| Scott Graham | f3a93d9a | 2018-02-26 20:47:03 | [diff] [blame] | 23 | `jiri update https://storage.googleapis.com/fuchsia-snapshots/<SDK_HASH_HERE>` |
| Scott Graham | d0aa2f4 | 2017-10-31 02:41:54 | [diff] [blame] | 24 | |
| 25 | If you are waiting for a Zircon CL to roll into the SDK, you can check the |
| 26 | status of the [Zircon |
| 27 | roller](https://luci-scheduler.appspot.com/jobs/fuchsia/zircon-roller). |
| 28 | Checking the bot's [list of |
| 29 | CLs](https://fuchsia-review.googlesource.com/q/owner:zircon-roller%40fuchsia-infra.iam.gserviceaccount.com) |
| 30 | might be useful too. |
| Scott Graham | ba1c9e1 | 2018-02-26 19:34:50 | [diff] [blame] | 31 | |
| Scott Graham | f3a93d9a | 2018-02-26 20:47:03 | [diff] [blame] | 32 | Another useful command, if the SDK was pulled by `cipd` (which it is in |
| Scott Graham | ba1c9e1 | 2018-02-26 19:34:50 | [diff] [blame] | 33 | Chromium-related projects like Crashpad, instead of directly pulling the |
| Scott Graham | c155b76f | 2018-02-26 19:38:42 | [diff] [blame] | 34 | .tar.gz), is: |
| Scott Graham | ba1c9e1 | 2018-02-26 19:34:50 | [diff] [blame] | 35 | |
| Scott Graham | f3a93d9a | 2018-02-26 20:47:03 | [diff] [blame] | 36 | `cipd describe fuchsia/sdk/linux-amd64 -version <CIPD_HASH_HERE>` |
| Scott Graham | ba1c9e1 | 2018-02-26 19:34:50 | [diff] [blame] | 37 | |
| 38 | This description will show the `jiri_snapshot` "tag" for the CIPD package which |
| Aidan Wolter | 7bc61d0 | 2019-01-03 00:56:49 | [diff] [blame] | 39 | corresponds to the SDK revision that's specified in `linux.sdk.sha1` here. |
