[roll] Roll infra/recipes [android] Use content hash as CIPD search tag

This ensures that we'll always upload and tag a new CIPD package when
the contents change, even if the build ID hasn't changed. This may
happen if the properties defining the set of files included in the
package changes without a new valid build being produced.

Rollers that depend on packages produced by this recipe will need to be
updated to track the "content_version" tag instead of the "bid" tag,
since "bid" will no longer be unique and thus no longer resolvable.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/952692
Original-Revision: 96a5b8eb32de97805a43cf11dab705b87de4fc7c
GitOrigin-RevId: 970cd990d4727a6f923a04d0cf6d0e02f0602ee1
Change-Id: I98ba5bbdbecf982b2726bb9d7c1974ee49997ed9
1 file changed
tree: e6190f0c7c5dacec7d2b9d998597d58f3343e18f
  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.