[lucicfg] Add graph.sorted_nodes function, rename 'exec' order to 'def'.

Also clarify that graph.children(..., 'def') and graph.parents(..., 'def')
sort nodes according to the order edges where defined, regardless of the order
of definition of nodes themselves.

On the other hand, sorted_nodes(..., 'def') sorts nodes by the order they were
declared in the graph.

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

Change-Id: If3ce2580c72ca3ccf99e0c55130c699a7b03abdc
Reviewed-on: https://chromium-review.googlesource.com/c/1394247
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
9 files changed
tree: afcbb5a4463ef02fe1379a5f2a8ab96957b7b6f5
  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.