[scheduler] Derive BuilderID from configs.

R=tandrii@chromium.org
BUG=1182002

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