OLD | NEW |
---|---|
(Empty) | |
1 Commit Queue Keywords | |
2 ===================== | |
3 | |
4 COMMIT | |
5 ------ | |
6 | |
7 If you want to test your CL through the commit queue but are not ready to commit the changes yet, you can add the following line to the CL description: | |
jcgregorio
2015/01/20 17:59:00
Wrap all paragraphs to 80 or 100 cols.
| |
8 | |
9 COMMIT=false | |
10 | |
11 The CQ will run through its list of verifiers (reviewer check, trybots, tree che ck, presubmit check), and will close the issue instead of committing it. | |
12 | |
13 CQ_INCLUDE_TRYBOTS | |
14 | |
15 Allows you to add arbitrary trybots to the CQ's list of default trybots. The CQ will block till these tryjobs pass just like the default list of tryjobs. | |
16 | |
17 This is the format of the values of this keyword: | |
18 | |
19 CQ_INCLUDE_TRYBOTS=master1:bot1,bot2;master2:bot3,bot4 | |
20 | |
21 Here are some real world examples: | |
22 | |
23 CQ_INCLUDE_TRYBOTS=tryserver.chromium:linux_layout_rel | |
24 | |
25 CQ_INCLUDE_TRYBOTS=tryserver.skia:Build-Ubuntu13.10-GCC4.8-NaCl-Release-Tryb ot | |
26 | |
27 CQ_EXCLUDE_TRYBOTS | |
28 | |
29 Allows you to remove trybots from the CQ's list of default trybots. Should only be used when particular builders are failing for reasons unrelated to your code changes. | |
30 | |
31 This is the format of the values of this keyword: | |
32 | |
33 CQ_EXCLUDE_TRYBOTS=master1:bot1,bot2;master2:bot3,bot4 | |
34 | |
35 Here are some real world examples: | |
36 | |
37 CQ_EXCLUDE_TRYBOTS=tryserver.chromium:win_chromium_compile_dbg | |
38 | |
39 CQ_EXCLUDE_TRYBOTS=tryserver.skia:Build-Win7-VS2010-x86-Debug-Trybot | |
40 | |
41 CQ_TRYBOTS | |
42 | |
43 Allows you to list every trybot that you want to run for your CL. | |
44 | |
45 This is the format of the values of this keyword: | |
46 | |
47 CQ_TRYBOTS=master1:bot1,bot2;master2:bot3,bot4 | |
48 | |
49 Here are some real world examples: | |
50 | |
51 CQ_TRYBOTS=tryserver.chromium:linux_chromium_gn_rel,linux_chromium_chromeos_ rel,android_dbg_triggered_tests,android_dbg,mac_chromium_rel,win_chromium_x64_re l | |
52 | |
53 CQ_TRYBOTS=tryserver.skia:Build-Win7-VS2010-x86-Debug-Trybot,Test-Ubuntu13.1 0-ShuttleA-NoGPU-x86_64-Debug-Trybot,Build-Ubuntu13.10-GCC4.8-x86_64-Release-Try bot,Build-Ubuntu13.10-Clang-x86_64-Debug-Trybot,Build-Mac10.8-Clang-x86_64-Relea se-Trybot | |
54 | |
55 TBR | |
56 --- | |
57 | |
58 If you are a Skia committer and cannot wait for a review then you can include th e TBR keyword in your CL's description. | |
59 | |
60 Example: | |
61 | |
62 TBR=rmistry@google.com | |
63 | |
64 NOTREECHECKS | |
65 | |
66 If you want to skip the tree status checks, to make the CQ commit a CL even if t he tree is closed, you can add the following line to the CL description: | |
67 | |
68 NOTREECHECKS=true | |
69 | |
70 This is discouraged, since the tree is closed for a reason. However, in rare cas es this is acceptable, primarily to fix build breakages (i.e., your CL will help in reopening the tree). | |
71 | |
72 NOPRESUBMIT | |
73 | |
74 If you want to skip the presubmit checks, add the following line to the CL descr iption: | |
75 | |
76 NOPRESUBMIT=true | |
77 | |
78 NOTRY | |
79 ----- | |
80 | |
81 If you cannot wait for the try job results, you can add the following line to th e CL description: | |
82 | |
83 NOTRY=true | |
84 | |
85 The CQ will then not run any try jobs for your change and will commit the CL as soon as the tree is open, assuming the presubmit check passes. | |
OLD | NEW |