Normally the Fuchsia SDK dependency is automatically updated to a recent build on a regular basis, by the Fuchsia SDK AutoRoll Bot.
Should you need to manually update the SDK dependency for some reason, then:
gsutil.uploadlink of the
gclient sync && ninja ...and make sure things go OK locally.
fuchsiatrybot. Tag the roll with
If you would like to build an SDK locally,
tools/fuchsia/local-sdk.py tries to do this (so you can iterate on ToT Fuchsia against your Chromium build), however it's simply a copy of the steps run on the bot above, and so may be out of date.
In order to sync a Fuchsia tree to the state matching an SDK hash, you can use:
jiri update https://storage.googleapis.com/fuchsia-snapshots/<SDK_HASH_HERE>
Another useful command, if the SDK was pulled by
cipd (which it is in Chromium-related projects like Crashpad, instead of directly pulling the .tar.gz), is:
cipd describe fuchsia/sdk/linux-amd64 -version <CIPD_HASH_HERE>
This description will show the
jiri_snapshot “tag” for the CIPD package which corresponds to the SDK revision that's specified in