[lucicfg] Add `sequence.next(name)` internal API.

Will be used to generate unique keys for luci.console_view_entry(builder=...)
nodes when they are used inline as:

    luci.console_view(
        entries = [
            luci.console_view_entry(builder=...),
        ],
    )

Values passed to luci.console_view_entry in this case are not sufficient to
generate a unique enough key.

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

Change-Id: I2b421b30b03080108c90ae97e6346f98a025155d
Reviewed-on: https://chromium-review.googlesource.com/c/1471045
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Nodir Turakulov <nodir@chromium.org>
6 files changed
tree: da583a0ee359033dac709f5bfe263758648ca7aa
  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.