[lucicfg] Create Chrome OS source tree test config proto.

This proto is intended as the output format for the Chrome OS source
tree testing config, as generated by lucicfg's Starlark interpretter.

The proto unfortunately needs to live in the lucicfg repo so that it can
be compiled into the binary. Rumor has it that the Go proto package will
eventually allow runtime inclusion of external protos.

BUG=chromium:922998
TEST=Built lucicfg and ran it over .star file that uses this new proto

Change-Id: Id1add14ee8d993329b0485c59a0f126fb1d22eb9
Reviewed-on: https://chromium-review.googlesource.com/c/1439863
Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Auto-Submit: Sean Abraham <seanabraham@chromium.org>
4 files changed
tree: 5eb78dd7edcdf9c454c2337db9b2280a29bf1e0e
  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. swarming/
  28. tokenserver/
  29. tools/
  30. tumble/
  31. vpython/
  32. web/
  33. .gitattributes
  34. .travis.yml
  35. AUTHORS
  36. codereview.settings
  37. CONTRIBUTING.md
  38. CONTRIBUTORS
  39. LICENSE
  40. OWNERS
  41. pre-commit-go.yml
  42. PRESUBMIT.py
  43. 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.