commit | 75020fd266c843308f7beb83967fe9561ecd9728 | [log] [tgz] |
---|---|---|
author | Vadim Shtayura <vadimsh@chromium.org> | Thu Oct 24 20:04:31 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Oct 24 20:04:31 2019 |
tree | 0ed8e2989f7185331b2f5c2480edfa45fb66ee47 | |
parent | 9d7afdd0461576e34aca31531315a210f9265f47 [diff] |
[lucicfg] Allow to populate some lucicfg.var(...) values via CLI flags. Together with `-emit-to-stdout` this allows to use lucicfg scripts as sort-of functions pluggable into e.g. bash scripts. R=tandrii@chromium.org BUG=1016462 Change-Id: I6be86e0a162b14241ff7b55e9e6bcb2a7557ed13 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/1875428 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
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.