commit | 83c1d10e6370742e590c4430f7988e6871f76dbf | [log] [tgz] |
---|---|---|
author | Ben Pastene <bpastene@chromium.org> | Thu Jan 04 20:30:13 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 04 20:30:13 2024 |
tree | a0479d34b461584b9ddbf481d300d7bd174ab065 | |
parent | f6709b2c1b3a745b5cbe1a471af8bbd4a240db71 [diff] |
infra: Define custom mega CQ run modes & enable it on mega cq builder Now that crbug.com/1483511 is fixed and we're out of the freeze, we should finally be able to hook-up the mega cq button in gerrit to an actual cq attempt. So this defines the two custom run_modes for the mega CQ & configures the mega-cq-launcher builder to be triggered by that run mode. The launcher will handle triggering sub-builds of real builders, so we don't need to list any other builder on these run modes for now. If/when we delete the launcher and use native CV functionality for the mega CQ, then we'd need to allowlist all relevant builders. ie: This TODO: https://source.chromium.org/chromium/chromium/src/+/main:infra/config/lib/builder_config.star;drc=dd5ca12dd573a863573e83f30486e7638aa43c60;l=793 But that's blocked on crbug.com/1483516. Bug: 1227778 Change-Id: I50a8a406eab29b5fbe8279a3a64864ac53b16258 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5147843 Reviewed-by: Garrett Beaty <gbeaty@google.com> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/main@{#1243083}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.