commit | 29abd193b6384a1822275613c9a6aa9ea8fd60a2 | [log] [tgz] |
---|---|---|
author | Nodir Turakulov <nodir@google.com> | Tue Apr 09 00:36:12 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Apr 09 00:36:12 2019 |
tree | a0e125a46043ca9710e3f6e320520a58efe0bbe0 | |
parent | a1640156ad3094111d84fbeeea2ff8c7242af7fe [diff] |
[bb] log: remove -json flag The JSON objects emitted by `bb log -json` do not include the log name. Otherwise, it is not obvious what JSON object format should be in case we add multi-build support to bb log. Change-Id: Ia34791bf1c42073b180bfaca8babe65e58caf18e Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/1558633 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Auto-Submit: Nodir Turakulov <nodir@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.