[lucicfg] Teach validate.relative_path to apply the path to a base.

To avoid doing string math manually to get rid of ".."'s.

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

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