| commit | 40266bdca3e0c5da0bfb4b4ffe2d6649c2c1f85f | [log] [tgz] |
|---|---|---|
| author | Vadim Shtayura <vadimsh@chromium.org> | Sat Jan 19 03:13:53 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Sat Jan 19 03:13:53 2019 |
| tree | 5a9f59c5d43b4fabc062fe8a7c1dbf7b29689476 | |
| parent | eaaf74bd3d57dba0568d36273de0913a19995fd2 [diff] |
[lucicfg] Add a way to provide "meta" configuration. This is configuration for the config generator itself. Stuff like where to place files and how to call LUCI Config. It can be set via core.meta(...) in *.star, or overriden through command line flags. R=tandrii@chromium.org, nodir@chromium.org BUG=833946 Change-Id: I109d5be20b73b8e1f72fe7293fba94e9b7b5d2e9 Reviewed-on: https://chromium-review.googlesource.com/c/1420019 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:
fetch infra cd infra/go eval `./env.py` cd src/go.chromium.org/luci
Contributing uses the same flow as Chromium contributions.