tree: 6e5f4ffd341f68b706dfee94aeb0f7b7625ad834 [path history] [tgz]
  1. GOMA_OWNERS
  2. OWNERS
  3. PRESUBMIT.py
  4. README.md
  5. buckets/
  6. consoles/
  7. dev.star
  8. dev/
  9. generated/
  10. generators/
  11. lib/
  12. lint-luci-milo.py
  13. luci-scheduler.cfg
  14. main.star
  15. notifiers.star
  16. project_pb2.py
  17. tricium-prod.cfg
  18. validators/
  19. versioned/
infra/config/README.md

IMPORTANT: If you see this in a branch which is not master, this directory has no effect and should be ignored.

This directory contains chromium project-wide configurations for Chrome Operations services. For example, cr-buildbucket.cfg defines builders.

Remember Change these configs on master branch only!

Currently active version can be checked at https://luci-config.appspot.com/#/projects/chromium .

The configuration files are currently in the process of being migrated to lucicfg/starlark. See https://chromium.googlesource.com/infra/luci/luci-go/+/HEAD/lucicfg/doc/README.md for more information on lucicfg/starlark. If a hand-written configuration file is still present alongside this file, you can modify that file directly.

The remainder of the configuration files are generated by starlark. The starlark configuration is rooted in main.star and dev.star, which execute other starlark files to generate a subset of the LUCI service configuration files to the generated subdirectory. A presubmit check enforces that the generated files are kept in sync with the generated output of the starlark configuration.

The starlark configuration also copies over the not-yet migrated files to the generated directory, so updating the hand-written configuration files will require re-‘generating’ the configuration.