[cipd] Add 'deployment-check' and 'deployment-repair' advanced commands.

'deployment-check' is equivalent to running 'cipd ensure' in dry run mode,
with paranoia enabled, re-ensuring already (supposedly) installed packages.

'deployment-repair' is same, but running for real (not in dry run), so the
repair logic in 'ensure' activates.

R=tandrii@chromium.org, iannucci@chromium.org
BUG=915278

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