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