898403b0c9
This reverts commit 583fd2ba9961137d9b7df5e9fc917f6cc7c82e80. Reason for revert: In the previous attempt, the shadow builders were blocking CQ. In this reland, it sets cq=None instead of experimental=True so that they are not triggered automatically(?) After confirming all builders work, I want to set cq to these builders, again. (ideally non-blocking builders.) Original change's description: > Revert "Add reclient CQ shadow builders as experimental" > > This reverts commit e149d4d1000424d897e72ea4ef7aa2b777842e8d. > > Reason for revert: Reason for revert: These builders seems blocking CQ. > http://screen/44GuRKkhNHdwj8j > > Original change's description: > > Add reclient CQ shadow builders as experimental > > > > FWIU, setting exprimental=True makes CQ builders non-blocking. > > If not, please revert this CL. > > > > Bug: b/243594984 > > Change-Id: Ia20e37f4fe9ce629d6fddc9ab8b652b5b8a00572 > > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/286522 > > Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> > > Auto-Submit: Junji Watanabe <jwata@google.com> > > Commit-Queue: Junji Watanabe <jwata@google.com> > > Cr-Commit-Position: refs/heads/main@{#38817} > > Bug: b/243594984 > Change-Id: Ie3dd7707a920c68c53cb80bf5f86737c7f559393 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/286543 > Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com> > Auto-Submit: Junji Watanabe <jwata@google.com> > Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> > Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#38818} Bug: b/243594984 Change-Id: I573124da0c63a56d9cdd81f637bc984487c98208 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/286544 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Junji Watanabe <jwata@google.com> Cr-Commit-Position: refs/heads/main@{#38820}
infra/config folder
This folder 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.
Uploading changes
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/
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.
Activating the changes
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.