commit | 4749df1b10b6d6fb810a1d88021d6c84ff081b2d | [log] [tgz] |
---|---|---|
author | Vadim Shtayura <vadimsh@chromium.org> | Thu Dec 20 22:03:09 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Dec 20 22:03:09 2018 |
tree | 5c1f43adc418cd32df2f66e30e3bbda77064ae3d | |
parent | 511486c4da79cfe73784dee7e826bef5c3cdbb65 [diff] |
[lucicfg] Show full key path in node.String(). This will be helpful for printing error messages involving ambiguities when builder with a same name is defined in multiple buckets. R=nodir@chromium.org, tandrii@chromium.org BUG=833946 Change-Id: I91bde848d8a45a4fd745f1a040d7d153d6b69b73 Reviewed-on: https://chromium-review.googlesource.com/c/1387628 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.