[projects.cfg] Update revision.

Effective latency due to caching when chaning IdentityConfig identities or
adding a new one has been documented to be expected behavior.

TBR=nodir@chromium.org

Change-Id: I7c7dce8d053efb1c7313cf0b3bd3bdb3a3e81eb7
Reviewed-on: https://chromium-review.googlesource.com/c/1487077
Reviewed-by: Felix Matenaar <fmatenaar@chromium.org>
Commit-Queue: Felix Matenaar <fmatenaar@chromium.org>
1 file changed
tree: 00e4614789311658fbe58e4a4b717bb1b4191959
  1. .gitattributes
  2. .travis.yml
  3. AUTHORS
  4. CONTRIBUTING.md
  5. CONTRIBUTORS
  6. LICENSE
  7. OWNERS
  8. PRESUBMIT.py
  9. README.md
  10. appengine/
  11. auth/
  12. buildbucket/
  13. cipd/
  14. client/
  15. codereview.settings
  16. common/
  17. config/
  18. cq/
  19. dm/
  20. examples/
  21. gce/
  22. grpc/
  23. hardcoded/
  24. logdog/
  25. luci_notify/
  26. lucicfg/
  27. lucictx/
  28. machine-db/
  29. milo/
  30. mmutex/
  31. mp/
  32. pre-commit-go.yml
  33. scheduler/
  34. scripts/
  35. server/
  36. starlark/
  37. swarming/
  38. tokenserver/
  39. tools/
  40. tumble/
  41. vpython/
  42. web/
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.