IMPORTANT: This branch only has an effect for branches that have projects set up in https://chrome-internal.googlesource.com/infradata/config/+/HEAD/configs/luci-config/projects.cfg
This directory contains chromium project-wide configurations for Chrome Operations services. For example, cr-buildbucket.cfg defines builders.
Currently active version can be checked at https://luci-config.appspot.com/#/projects/chromium .
The configuration is written using starlark, which is executed using lucicfg to generate the raw cfg files located in generated. See https://chromium.googlesource.com/infra/luci/luci-go/+/HEAD/lucicfg/doc/README.md for more information on lucicfg/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. A presubmit check enforces that the generated files are kept in sync with the output of the starlark configuration.
The configuration rooted at main.star defines the LUCI services configuration for the chromium project on the production instance of LUCI. The configuration is responsible for generating the raw configuration files that do not end in -dev.cfg as well as the markdown file cq-builders.md. Starlark files in the following directories are consumed by the configuration:
The configuration rooted at dev.star defines the LUCI services configuration for the chromium project on the dev instance of LUCI. This configuration consumes starlark files under the dev directory and is responsible for generating the raw configuration files ending in -dev.cfg.
In order to get syntax highlighting, the Bazel can be installed.
In order to get “go to definition” to work, an extra language server needs to be available for the Bazel extension. This currently requires applying a custom patch on top of the bazel-lsp project and compiling the language server binary, then using it via settings.json in VS Code. See the //tools/vscode/bazel_lsp/README.md for more details.