[cipd] Refactoring plugins implementation, part 2.

The package with cipd.Client no longer depends on gRPC
servers.

R=tandrii@chromium.org, jwata@google.com

Change-Id: I59ee10b534b242197b61fdd76944477e38d9a7f6
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/2644004
Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
7 files changed
tree: e2caf317db68f2bc7180ada708de94d4e103acbc
  1. .gitallowed
  2. .gitattributes
  3. .gitignore
  4. AUTHORS
  5. CONTRIBUTING.md
  6. CONTRIBUTORS
  7. LICENSE
  8. OWNERS
  9. PRESUBMIT.py
  10. README.md
  11. WATCHLISTS
  12. appengine/
  13. auth/
  14. buildbucket/
  15. casviewer/
  16. cipd/
  17. client/
  18. cmdrunner/
  19. codereview.settings
  20. common/
  21. config/
  22. cq/
  23. cv/
  24. dm/
  25. examples/
  26. gae/
  27. gce/
  28. grpc/
  29. hardcoded/
  30. led/
  31. logdog/
  32. luci_notify/
  33. lucicfg/
  34. lucictx/
  35. luciexe/
  36. machine-db/
  37. milo/
  38. mmutex/
  39. mp/
  40. resultdb/
  41. scheduler/
  42. server/
  43. starlark/
  44. swarming/
  45. tokenserver/
  46. tools/
  47. tumble/
  48. vpython/
  49. web/
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.