Google Git
Sign in
chromium / infra / luci / luci-go / e2281b0154c8e4e8ed60fd3881efdbde21c2b6aa
commite2281b0154c8e4e8ed60fd3881efdbde21c2b6aa[log] [tgz]
authorVadim Shtayura <vadimsh@chromium.org>Tue Jan 29 23:47:20 2019
committerCommit Bot <commit-bot@chromium.org>Tue Jan 29 23:47:20 2019
treeeab6f2dffa5705ca6522390a2084b549ab4a8010
parent4dbd9f5d50c2372ca2bc4ae7d25f986a492e8cfd [diff]
[lucicfg] Use subcommands.Section as subcommands separator.

Something has changed in 'subcommands' and running "lucicfg -unknown" causes
a panic instead of reporting an error. Using subcommands.Section(...) serves
as a workaround.

R=tandrii@chromium.org
BUG=833946

Change-Id: I14a287e1822053599b4f1c0d68e522bfe1e59072
Reviewed-on: https://chromium-review.googlesource.com/c/1441676
Auto-Submit: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
1 file changed
tree: eab6f2dffa5705ca6522390a2084b549ab4a8010
  1. appengine/
  2. auth/
  3. buildbucket/
  4. cipd/
  5. client/
  6. common/
  7. config/
  8. cq/
  9. dm/
  10. examples/
  11. gce/
  12. grpc/
  13. hardcoded/
  14. infra/
  15. logdog/
  16. luci_notify/
  17. lucicfg/
  18. lucictx/
  19. machine-db/
  20. milo/
  21. mmutex/
  22. mp/
  23. scheduler/
  24. scripts/
  25. server/
  26. starlark/
  27. swarming/
  28. tokenserver/
  29. tools/
  30. tumble/
  31. vpython/
  32. web/
  33. .gitattributes
  34. .travis.yml
  35. AUTHORS
  36. codereview.settings
  37. CONTRIBUTING.md
  38. CONTRIBUTORS
  39. LICENSE
  40. OWNERS
  41. pre-commit-go.yml
  42. PRESUBMIT.py
  43. README.md
README.md

luci-go: LUCI services and tools in Go

GoDoc

Installing

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

Contributing uses the same flow as Chromium contributions.