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