Remove Win8 bots since they no longer provide value

Bug: chromium:1281336
Change-Id: I80d0ca5debab0c509693f9e1289021e423716496
Reviewed-by: Mirko Bonadei <>
Commit-Queue: Christoffer Jansson <>
4 files changed
tree: 06f8acc2b8ad410b6939cf3fedfca2eac95d0ff3
  1. luci-notify/
  5. codereview.settings
  6. commit-queue.cfg
  8. console-header.textpb
  9. cr-buildbucket.cfg
  10. luci-logdog.cfg
  11. luci-milo.cfg
  12. luci-notify.cfg
  13. luci-scheduler.cfg
  14. project.cfg
  15. realms.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 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 you should run lucicfg generate 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 -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.