Google Git
Sign in
fuchsia / infra / config / afe248cf7b7c8485e8a8ae3319d01b9fba3969f0
commitafe248cf7b7c8485e8a8ae3319d01b9fba3969f0[log] [tgz]
authorPetr Hosek <phosek@google.com>Fri Jun 28 13:25:58 2019 -0700
committerPetr Hosek <phosek@google.com>Fri Jun 28 13:25:58 2019 -0700
treeb75b6261c095df55eb8e76617195f011ea3939cf
parent96021233e9d5545d06d38f7f3b766865c2b4deaa [diff]
Switch Dart trigger back to use the master branch

Bug: INTK-1171 #done
Change-Id: I85651d0df755a5a86fd125f10e98473659569fce
3 files changed
tree: b75b6261c095df55eb8e76617195f011ea3939cf
  1. generated/
  2. lib/
  3. manifest/
  4. repositories/
  5. .gitignore
  6. .style.yapf
  7. AUTHORS
  8. LICENSE
  9. main.star
  10. MAINTAINERS
  11. OWNERS
  12. PATENTS
  13. README.md
README.md

Config

This repository contains configuration files for infra services.

For the most part, the actual configs consumed by LUCI live under generated/. Those files are generated by executing the .star files at the root of the repository. Don't edit the generated files directly. Instead, edit the Starlark files and execute them to regenerate the generated/ files.

If you've checked out the infra repos using our Jiri manifest, then you should have a git hook that will automatically execute the starlark code and regenerate generated/*.cfg on git commit.

To manually execute the Starlark code, run:

../../fuchsia-infra/prebuilt/tools/lucicfg generate ./main.star

Or if you have lucicfg in your PATH, you can execute the .star files directly:

./main.star

References