[isolate] Don't directly use SHA1 from tar_archiver.go.

R=maruel@chromium.org, tandrii@chromium.org

Change-Id: I876a6d39a39cb5a94121446c0defc225a76b7ec6
Reviewed-on: https://chromium-review.googlesource.com/c/1290105
Auto-Submit: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Marc-Antoine Ruel <maruel@chromium.org>
Commit-Queue: Marc-Antoine Ruel <maruel@chromium.org>
1 file changed
tree: 69d347ab405ae2461932a59b7f1171f058bf68a8
  1. appengine/
  2. auth/
  3. buildbucket/
  4. cipd/
  5. client/
  6. common/
  7. config/
  8. dm/
  9. examples/
  10. grpc/
  11. hardcoded/
  12. infra/
  13. logdog/
  14. luci_notify/
  15. lucictx/
  16. machine-db/
  17. milo/
  18. mmutex/
  19. mp/
  20. scheduler/
  21. scripts/
  22. server/
  23. skylark/
  24. tokenserver/
  25. tools/
  26. tumble/
  27. vpython/
  28. web/
  29. .travis.yml
  30. AUTHORS
  31. codereview.settings
  32. CONTRIBUTING.md
  33. CONTRIBUTORS
  34. LICENSE
  35. OWNERS
  36. pre-commit-go.yml
  37. PRESUBMIT.py
  38. 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.