[lucicfg] Implement all fields of core.builder(...) except 'recipe'.

'recipe' field needs a definition of core.recipe(...) rule. It will be done
later.

The following proto fields we explicitly do not support:
  * All mixin related stuff.
  * 'category' (was never used)
  * 'auto_builder_dimension' (shouldn't be necessary with Starlark)
  * recipe.properties (we always use properties_j)

R=nodir@chromium.org, tandrii@chromium.org
BUG=833946

Change-Id: Iac635f6f28a946e2fb133f42c377f8b901c4a3e5
Reviewed-on: https://chromium-review.googlesource.com/c/1399994
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Nodir Turakulov <nodir@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
5 files changed
tree: b7ee2e7b68cc342bd2ba408873797027a0241edd
  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. tokenserver/
  28. tools/
  29. tumble/
  30. vpython/
  31. web/
  32. .travis.yml
  33. AUTHORS
  34. codereview.settings
  35. CONTRIBUTING.md
  36. CONTRIBUTORS
  37. LICENSE
  38. OWNERS
  39. pre-commit-go.yml
  40. PRESUBMIT.py
  41. 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.