|author||Andrey Logvin <firstname.lastname@example.org>||Thu Feb 04 13:03:49 2021|
|committer||Commit Bot <email@example.com>||Mon Feb 15 14:24:46 2021|
Reland "Temporarily remove ios_sim_x64_dbg_ios12 from cq" This is a reland of 98a7bc578187b2b97742414810b7a7281cbbbaa8 The issue is still happening, so let's remove from CQ again. Original change's description: > Temporarily remove ios_sim_x64_dbg_ios12 from cq > > Bug: chromium:1174112 > Change-Id: I04967cf7e4f7d3814291b5bc5700daf0070efa87 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/205625 > Commit-Queue: Andrey Logvin <firstname.lastname@example.org> > Reviewed-by: Mirko Bonadei <email@example.com> Bug: chromium:1174112 Change-Id: Ibf677771a5b7932ca8cd9531849d5688dea9f334 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/207429 Reviewed-by: Andrey Logvin <firstname.lastname@example.org> Commit-Queue: Mirko Bonadei <email@example.com>
This branch contains WebRTC project-wide configurations for Chrome infra services, mainly the CI system (console).
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.
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.