commit | 96021233e9d5545d06d38f7f3b766865c2b4deaa | [log] [tgz] |
---|---|---|
author | Gary Miguel <garymm@google.com> | Fri Jun 28 11:16:11 2019 -0700 |
committer | Gary Miguel <garymm@google.com> | Fri Jun 28 11:24:09 2019 -0700 |
tree | cb0e64b5f91b5defc462237577336da7c7681309 | |
parent | 5ba64b5de9a96342ae88e938997ebf82fe58e23c [diff] |
Move tricium checks to prod, and add lint I don't see any reason this needs to be restricted to the project-fuchsia-tricium-whitelist at this point. And running govet is useful since this repo contains Go code. Change-Id: I393125e1bff84aa5ae14d533266b8fa7c2ebd4f0
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