commit | 1bfafa939c0428183b55d5e0263537d094639bc3 | [log] [tgz] |
---|---|---|
author | Ben Pastene <bpastene@chromium.org> | Wed Apr 24 20:34:10 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 24 20:34:10 2024 |
tree | 91f4554137bdf3b49af936f84056170c8e34d049 | |
parent | 058ed3f109239f879856960b608c6ba994f53c31 [diff] |
infra: Let chromium-try-builder@ account trigger builds in try.shadow Similar to how the service account can trigger in the normal try bucket, this allows it to trigger in the shadow one as well. This is mainly to enable led builds of the mega-cq, which is failing now(?) to trigger: https://ci.chromium.org/ui/p/chromium/builders/try.shadow/mega-cq-launcher/24/infra Bug: 329482484 Change-Id: I6ede83717616b7cf2e6c84c373a8c84f97e5f2d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5484223 Reviewed-by: Garrett Beaty <gbeaty@google.com> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/main@{#1292064}
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.