commit | c71698b1bdeebc5816e3adc826bdc73b7b11f284 | [log] [tgz] |
---|---|---|
author | Ming-Ying Chung <mych@chromium.org> | Fri Mar 07 19:11:51 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 07 19:11:51 2025 |
tree | f8d4fc942c8951f3f5eefa7085117f47e7e4b434 | |
parent | 2db8850d8a1e3555131e10a010d8cacbe885bd8e [diff] |
[translatekit] Move internal CI builder waterfall to public src (Part 2) Another CL https://crrev.com/i/8081379 is sent out to remove it from internal config. These builders were originally added by https://crrev.com/i/8023009. Another CL is sent out to remove them from internal configs. Per [offline discussion][1], for Try builders to run the [internal model_validation recipe][2], the CI builder it mirrors needs to have public `testing/buildbot/*.json` config. Also run the following commands to generate configs: ```sh lucicfg fmt lucicfg generate infra/config/main.star testing/buildbot/generate_buildbot_json.py ``` [1]: https://screenshot/7mm93cbE5UEbdJT [2]: https://source.corp.google.com/h/chromium/infra/infra_superproject/+/main:build_internal/recipes/recipes/chrome_intelligence/model_validation.py;l=206-207;drc=1ab44a40dc3926ccb0d15c86c01187e3b5d0891e Bug: 394439535, 396009228 Change-Id: I6d9f613f57110170349fcae1d17633d9e3b405f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6332297 Reviewed-by: Marco Georgaklis <mgeorgaklis@google.com> Reviewed-by: Gregory Guterman <guterman@google.com> Commit-Queue: Ming-Ying Chung <mych@chromium.org> Cr-Commit-Position: refs/heads/main@{#1429632}
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.