| commit | 2b0245c53fa39d48b04a73e022d80cd3f81f5b08 | [log] [tgz] |
|---|---|---|
| author | Jeremy Leconte <jleconte@webrtc.org> | Mon Feb 28 14:04:31 2022 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 01 21:01:19 2022 |
| tree | 80620391a456425c1c2d836f44f1684b0779da57 | |
| parent | ec86a699e85f37f99623d1b7980c32f90adca390 [diff] |
Use standalone recipe for iOS try builders. This CL is to submit along with https://chromium-review.googlesource.com/c/chromium/tools/build/+/3484059. Bug: webrtc:12768 Change-Id: I8118a3e6db70d2e9cee04a46a8ccf29414d83c7b Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/252980 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Jeremy Leconte <jleconte@google.com>
This branch contains WebRTC project-wide configurations for Chrome infra services, mainly the CI system (console).
*.cfg files are the actual configuration that LUCI looks at. They are in protocol buffer text format. For example, cr-buildbucket.cfg defines builders.
However, they are all automatically generated from the Starlark script config.star that defines a unified config using lucicfg. The main body of the config is at the bottom of the file, following all the helper definitions.
lucicfg should be available as part of depot_tools. After editing config.star you should run lucicfg generate config.star to re-generate *.cfg files. Check the diffs in generated files to confirm that your change worked as expected. Both the code change and the generated changes need to be committed together.
It is recommended to have a separate checkout for this branch, so switching to/from it does not populate/delete all files in the master branch.
Initial setup:
git clone https://webrtc.googlesource.com/src/ -b infra/config --single-branch config cd config git config depot-tools.upstream origin/infra/config
Now you can create a new branch to make changes:
git new-branch add-new-builder # edit/generate files git commit -a git cl upload
Changes can be reviewed on Gerrit and submitted with commit queue as usual.
Any changes to this directory go live soon after landing, without any additional steps. You can see the status or force a refresh of the config at luci-config.