|author||Oleh Prypin <firstname.lastname@example.org>||Fri Apr 05 13:03:03 2019|
|committer||Commit Bot <email@example.com>||Fri Apr 12 12:41:52 2019|
Fix email templates according to backwards-incompatible change https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/1541679/13/luci_notify/notify/emailgen.go#45 Note: what used to be (e.g.) "webrtc/ci/Linux Asan" will now just be "Linux Asan", that is intentional, I decided not to port the other parts. Change-Id: I2bfc0be1fe9e90cbb315a6955d50395d9c10ceaf Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/131332 Reviewed-by: Oleh Prypin <firstname.lastname@example.org> Commit-Queue: Oleh Prypin <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.