[roll] Roll infra/recipes [cas_util] Move hardlink logic into cipd_util

The `cas` CLI now supports processing symlinks that point outside the
staging directory, so we can use `api.file.symlink_tree()` to construct
trees of files that get uploaded to CAS instead of the custom
implementation. However, we still need the custom implementation for
CIPD uploads, which don't support following symlinks that point outside
the upload root.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/825916
Original-Revision: 4636e0d6cd4e0ef28176b0e23b416302e08a8268
GitOrigin-RevId: f93fe2da74147f38bca991410c377bbac5e0f6c7
Change-Id: Ib0c91609009d9fe70ec714422381825ef4201f7e
1 file changed
tree: e0282ff1dab028371fea4814520682aca1d8183c
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.