1 Commit Queue Keywords 2 ===================== 3 4 COMMIT 5 ------ 6 7 If you are working on experimental code and do not want to risk accidentally 8 submitting the change via the CQ, then you can mark it with "COMMIT=false". 9 The CQ will immediately abandon the change if it contains this option. 10 To do a dry run through the CQ please use Rietveld's [dry run](https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/G5-X0_tfmok) feature. 11 12 COMMIT=false 13 14 The CQ will run through its list of verifiers (reviewer check, trybots, tree check, 15 presubmit check), and will close the issue instead of committing it. 16 17 CQ_INCLUDE_TRYBOTS 18 19 Allows you to add arbitrary trybots to the CQ's list of default trybots. 20 The CQ will block till these tryjobs pass just like the default list of tryjobs. 21 22 This is the format of the values of this keyword: 23 24 CQ_INCLUDE_TRYBOTS=master1:bot1,bot2;master2:bot3,bot4 25 26 Here are some real world examples: 27 28 CQ_INCLUDE_TRYBOTS=tryserver.chromium:linux_layout_rel 29 30 CQ_INCLUDE_TRYBOTS=tryserver.skia:Build-Mac10.9-Clang-x86_64-Debug 31 32 CQ_EXCLUDE_TRYBOTS 33 34 Allows you to remove trybots from the CQ's list of default trybots. Should only be 35 used when particular builders are failing for reasons unrelated to your code changes. 36 37 This is the format of the values of this keyword: 38 39 CQ_EXCLUDE_TRYBOTS=master1:bot1,bot2;master2:bot3,bot4 40 41 Here are some real world examples: 42 43 CQ_EXCLUDE_TRYBOTS=tryserver.chromium:win_chromium_compile_dbg 44 45 CQ_EXCLUDE_TRYBOTS=tryserver.skia:Build-Win7-VS2010-x86-Debug-Trybot 46 47 CQ_TRYBOTS 48 49 Allows you to list every trybot that you want to run for your CL. 50 51 This is the format of the values of this keyword: 52 53 CQ_TRYBOTS=master1:bot1,bot2;master2:bot3,bot4 54 55 Here are some real world examples: 56 57 CQ_TRYBOTS=tryserver.chromium:linux_chromium_gn_rel,linux_chromium_chromeos_rel, 58 android_dbg_triggered_tests,android_dbg,mac_chromium_rel,win_chromium_x64_rel 59 60 CQ_TRYBOTS=tryserver.skia:Build-Win7-VS2010-x86-Debug-Trybot, 61 Test-Ubuntu13.10-ShuttleA-NoGPU-x86_64-Debug-Trybot, 62 Build-Ubuntu13.10-GCC4.8-x86_64-Release-Trybot, 63 Build-Ubuntu13.10-Clang-x86_64-Debug-Trybot,Build-Mac10.8-Clang-x86_64-Release-Trybot 64 65 TBR 66 --- 67 68 If you are a Skia committer and cannot wait for a review, 69 then you can include the TBR keyword in your CL's description. 70 71 Example: 72 73 TBR=rmistry (a] google.com 74 75 NOTREECHECKS 76 77 If you want to skip the tree status checks, to make the CQ commit a CL even if the tree is closed, 78 you can add the following line to the CL description: 79 80 NOTREECHECKS=true 81 82 This is discouraged, since the tree is closed for a reason. However, in rare cases this is acceptable, 83 primarily to fix build breakages (i.e., your CL will help in reopening the tree). 84 85 NOPRESUBMIT 86 87 If you want to skip the presubmit checks, add the following line to the CL description: 88 89 NOPRESUBMIT=true 90 91 NOTRY 92 ----- 93 94 If you cannot wait for the try job results, you can add the following line to the CL description: 95 96 NOTRY=true 97 98 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. 99 100 NO_MERGE_BUILDS 101 --------------- 102 103 This keyword prevents the Skia build masters from building this commit with others. Use it when your 104 commit may have effects that you don't want mis-attributed to other commits. Just include the keyword 105 somewhere in the commit message: 106 107 NO_MERGE_BUILDS 108
