commit | 3fca1b70ed44e01fb5fba74c730562b2416b7fd2 | [log] [tgz] |
---|---|---|
author | Vadim Shtayura <vadimsh@chromium.org> | Thu Jan 24 19:24:51 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Jan 24 19:24:51 2019 |
tree | d9ee9a852f5c05a7e32f70e4a43f010ae022abac | |
parent | 3897842737faad2053e6ba4c1b5c6b4c3590a605 [diff] |
[lucicfg] Add few utility methods to ConfigSet. They'll be used to produce some not-entirely-useless -json-output for 'generate' subcommand. R=tandrii@chromium.org, nodir@chromium.org BUG=833946 Change-Id: I2cb2a30df0fb6b9743372809a972fe9465fc900e Reviewed-on: https://chromium-review.googlesource.com/c/1433578 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@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.