0

[docs] Update docs to reflect current Fuchsia sdk

Bug: None
Test: None
Change-Id: Ib9daa3f4e144c3c7b62d7d472cb631f2e6db41a5
Reviewed-on: https://chromium-review.googlesource.com/c/1393892
Reviewed-by: Wez <wez@chromium.org>
Commit-Queue: Aidan Wolter <awolter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#619549}
This commit is contained in:
Aidan Wolter
2019-01-03 00:56:49 +00:00
committed by Commit Bot
parent e8b1c0c176
commit 7bc61d0bfa

@ -6,10 +6,10 @@ on a regular basis, by the [Fuchsia SDK AutoRoll Bot](https://fuchsia-sdk-chromi
Should you need to manually update the SDK dependency for some reason, then:
1. Check the [Fuchsia-side
job](https://luci-scheduler.appspot.com/jobs/fuchsia/sdk-garnet-x64-linux)
job](https://luci-scheduler.appspot.com/jobs/fuchsia/sdk-topaz-x64-linux)
for a recent green archive. On the "SUCCEEDED" link, copy the SHA-1 from the
`gsutil.upload` link of the `upload fuchsia-sdk` step.
0. Put that into Chromium's src.git `build/fuchsia/sdk.sha1`.
0. Put that into Chromium's src.git `build/fuchsia/linux.sdk.sha1`.
0. `gclient sync && ninja ...` and make sure things go OK locally.
0. Upload the roll CL, making sure to include the `fuchsia` trybot. Tag the roll
with `Bug: 707030`.
@ -36,4 +36,4 @@ Chromium-related projects like Crashpad, instead of directly pulling the
`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 `sdk.sha1` here.
corresponds to the SDK revision that's specified in `linux.sdk.sha1` here.