Halve the frequency of 'Auto-roll - WebRTC DEPS'

It runs so frequently to be able to find culprits more easily. But that has been much less of a problem lately.

Change-Id: I037411e9a5027e2174493ca998f96784cf9f3454
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/143682
Reviewed-by: Mirko Bonadei <mbonadei@google.com>
Commit-Queue: Oleh Prypin <oprypin@webrtc.org>
2 files changed
tree: 5738b214a319fe12d210876cb4f05ee823bf3172
  2. README.md
  3. codereview.settings
  4. commit-queue.cfg
  5. config.star
  6. console-header.textpb
  7. cr-buildbucket.cfg
  8. luci-logdog.cfg
  9. luci-milo.cfg
  10. luci-notify.cfg
  11. luci-notify/
  12. luci-scheduler.cfg
  13. project.cfg

infra/config branch

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.

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/ -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.

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.