[roll] Roll fuchsia [scripts] Run incremental publisher with time versioning

The ffx repository server has a TUF client, which tracks the versions of
the TUF metadata. We generally generate metadata where we use the latest
time as the version number, rather than monotonically increasing the
number. This allows us to do a `fx clean-build`, and the TUF metadata
to be correct.

Unfortunately we were running the incremental publisher without time
versioning. So if a user does `fx clean && fx test ...`, this can cause
a new TUF repository to be created, where the metadata version is 1.
TUF considers this a rollback attack, and will reject the metadata.

This avoids that case by enabling time versioning in all the places
where we use the incremental publisher.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/831298
Original-Revision: 7eded24645140e705401cb92b749a751b9e3d41a
GitOrigin-RevId: 9a5bc342f6d755d4c95bfb8367e00298a8c61fe9
Change-Id: I5deafeec08b9a042e5273df4586621bb5c9352e3
1 file changed
tree: f699bf7ffc3d92859fffe99cbc07de727fe3523a
  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.