docs/updating_clang.md - Issue 2940263003: Fix a small mistake in updating_clang.md.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: docs/updating_clang.md

Issue 2940263003: Fix a small mistake in updating_clang.md. (Closed)

Patch Set: Created 3 years, 6 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « no previous file | no next file » | no next file with comments »

OLD	NEW
1 # Updating clang	1 # Updating clang

2	2

3 1. Sync your Chromium tree to the latest revision to pick up any plugin	3 1. Sync your Chromium tree to the latest revision to pick up any plugin

4 changes	4 changes

5 1. Run `python tools/clang/scripts/upload_revision.py --clang_revision=NNNN`	5 1. Run `python tools/clang/scripts/upload_revision.py NNNN`

6 with the target LLVM SVN revision number. This creates a roll CL on a new	6 with the target LLVM SVN revision number. This creates a roll CL on a new

7 branch, uploads it and starts tryjobs that build the compiler binaries into	7 branch, uploads it and starts tryjobs that build the compiler binaries into

8 a staging bucket on Google Cloud Storage (GCS).	8 a staging bucket on Google Cloud Storage (GCS).

9 1. If the clang upload try bots succeed, copy the binaries from the staging	9 1. If the clang upload try bots succeed, copy the binaries from the staging

10 bucket to the production one. For example:	10 bucket to the production one. For example:

11	11

12 ```	12 ```

13 $ export rev=123456-1	13 $ export rev=123456-1

14 $ for x in Linux_x64 Mac Win ; do \	14 $ for x in Linux_x64 Mac Win ; do \

15 gsutil cp -n -a public-read gs://chromium-browser-clang-staging/$x/clang-$re v.tgz \	15 gsutil cp -n -a public-read gs://chromium-browser-clang-staging/$x/clang-$re v.tgz \

(...skipping 14 matching lines...) Expand all Loading...
30 ```	30 ```

31 git cl try &&	31 git cl try &&

32 git cl try -m tryserver.chromium.mac -b mac_chromium_asan_rel_ng &&	32 git cl try -m tryserver.chromium.mac -b mac_chromium_asan_rel_ng &&

33 git cl try -m tryserver.chromium.linux -b linux_chromium_chromeos_dbg_ng \	33 git cl try -m tryserver.chromium.linux -b linux_chromium_chromeos_dbg_ng \

34 -b linux_chromium_chromeos_asan_rel_ng -b linux_chromium_msan_rel_ng &&	34 -b linux_chromium_chromeos_asan_rel_ng -b linux_chromium_msan_rel_ng &&

35 git cl try -m tryserver.blink -b linux_trusty_blink_rel	35 git cl try -m tryserver.blink -b linux_trusty_blink_rel

36 ```	36 ```

37 1. Commit roll CL from the first step	37 1. Commit roll CL from the first step

38 1. The bots will now pull the prebuilt binary, and goma will have a matching	38 1. The bots will now pull the prebuilt binary, and goma will have a matching

39 binary, too.	39 binary, too.

OLD	NEW